unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zackw@panix.com>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: glibc at the Toolchains microconference at LPC 2019
Date: Thu, 27 Jun 2019 11:57:46 -0400	[thread overview]
Message-ID: <CAKCAbMg8DFw2V0-B0DmoM3+P9MnegroSp_2P7tdg+QqbydH_VQ@mail.gmail.com> (raw)
In-Reply-To: <20190627093928.GA25423@altlinux.org>

On Thu, Jun 27, 2019 at 5:39 AM Dmitry V. Levin <ldv@altlinux.org> wrote:
>
> On Wed, Jun 26, 2019 at 05:04:52PM -0400, Carlos O'Donell wrote:
> [...]
> > Could you please review the language here:
> > https://sourceware.org/glibc/wiki/Consensus#WIP:_Kernel_syscalls_wrappers
>
> I suggest adding that there is no need to add wrappers for those syscalls
> that already have dedicated libraries.
>
> For example, such multiplexers as bpf(2) and keyctl(2) already have
> dedicated libraries (libbpf and libkeyutils, respectively) that provide
> APIs on top of these raw syscalls.

I specifically disagree with this.  The existence of these dedicated
libraries does not mean that there is no need for a minimal wrapper in
the C library.  In fact, providing a minimal wrapper in the C library
would make the implementation of dedicated libraries easier, since
they can concentrate on designing their higher-level API rather than
wasting engineering effort on system call wrappers.  glibc has already
done all of the low-level work necessary.

I am a little disappointed to see that Linux is still inventing new
multiplexed system calls, though.  I thought that was demonstrated to
be a bad idea back in the days of __NR_ipc.

zw

  parent reply	other threads:[~2019-06-27 15:58 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26 16:01 glibc at the Toolchains microconference at LPC 2019 Florian Weimer
2019-06-26 16:39 ` Dmitry V. Levin
2019-06-26 16:50   ` Zack Weinberg
2019-06-26 16:56     ` Florian Weimer
2019-06-26 17:40       ` Zack Weinberg
2019-06-26 20:33       ` Carlos O'Donell
2019-06-26 20:39         ` Christian Brauner
2019-06-26 20:58           ` Carlos O'Donell
2019-06-26 17:28     ` Yann Droneaud
2019-06-26 17:41     ` Christian Brauner
2019-06-26 21:04       ` Carlos O'Donell
2019-06-27  9:39         ` Dmitry V. Levin
2019-06-27 10:05           ` Szabolcs Nagy
2019-06-27 10:18             ` Christian Brauner
2019-06-27 13:05             ` Dmitry V. Levin
2019-06-27 15:57           ` Zack Weinberg [this message]
2019-06-27 17:21             ` Florian Weimer
2019-06-27 20:07               ` Carlos O'Donell
2019-06-27 20:53             ` wrappers for multiplexed syscalls (was Re: glibc at the Toolchains microconference at LPC 2019) Dmitry V. Levin
2019-06-27 21:22               ` Florian Weimer
2019-06-28 21:20                 ` Dmitry V. Levin
2019-06-28 21:35                   ` Florian Weimer
2019-06-29  1:52                     ` Zack Weinberg
2019-06-29  6:27                       ` Florian Weimer
2019-06-27 13:22         ` glibc at the Toolchains microconference at LPC 2019 Zack Weinberg
2019-06-27 14:10         ` syscall wrappers policy (was re: glibc at the Toolchains microconference) Zack Weinberg
2019-06-27 15:48           ` DJ Delorie
2019-06-27 16:02             ` Zack Weinberg
2019-06-27 16:50           ` Carlos O'Donell
2019-06-27 17:45 ` glibc at the Toolchains microconference at LPC 2019 Maciej Rozycki
2019-07-08 12:57   ` Florian Weimer
2019-07-08 16:06     ` Paul Eggert
2019-07-19 11:49       ` Florian Weimer
2019-09-14  4:33         ` Maciej W. Rozycki
2019-09-14 11:53           ` Dmitry V. Levin
2019-09-14 14:02             ` Maciej W. Rozycki
2019-07-09  0:14     ` Dmitry V. Levin
2019-09-16 13:26     ` Christian Brauner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKCAbMg8DFw2V0-B0DmoM3+P9MnegroSp_2P7tdg+QqbydH_VQ@mail.gmail.com \
    --to=zackw@panix.com \
    --cc=carlos@redhat.com \
    --cc=ldv@altlinux.org \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).