From: "Ulrich Drepper" <drepper@gmail.com>
To: "Eric Dumazet" <dada1@cosmosbay.com>
Cc: "Ulrich Drepper" <drepper@redhat.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mingo@elte.hu, tglx@linutronix.de, torvalds@linux-foundation.org
Subject: Re: [PATCHv5 4/5] Allow setting O_NONBLOCK flag for new sockets
Date: Sat, 24 Nov 2007 08:11:38 -0800 [thread overview]
Message-ID: <a36005b50711240811g1fdca17fwe8534ebe8ece6432@mail.gmail.com> (raw)
In-Reply-To: <4747E0C6.5010900@cosmosbay.com>
On Nov 24, 2007 12:28 AM, Eric Dumazet <dada1@cosmosbay.com> wrote:
> OK, but maybe for consistency, we might accept the two mechanisms.
It's not a question of the kernel interface. The issue with all these
extensions is the userlevel interface. Ideally no new userlevel
interface is needed. This is the case for open() and incidentally
also for this case (through the flags parameter for recvmsg). For
socket(), accept(), the situation is unfortunately different and we
need a new interface.
With your proposed patch, we would have to introduce another recvmsg()
interface to take advantage of the additional functionality. This
just doesn't make any sense. This is no contest in aesthetics. You
first have to think about the interface presented to the programmer at
userlevel and then design the syscall interface. This is how
MSG_CMSG_CLOEXEC came about.
prev parent reply other threads:[~2007-11-24 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 7:28 Ulrich Drepper
2007-11-24 7:17 ` Eric Dumazet
2007-11-24 7:43 ` Ulrich Drepper
2007-11-24 8:28 ` Eric Dumazet
2007-11-24 16:11 ` Ulrich Drepper [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a36005b50711240811g1fdca17fwe8534ebe8ece6432@mail.gmail.com \
--to=drepper@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®