From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] alternative to sys_indirect, part 1
Date: Thu, 24 Apr 2008 20:49:32 +0400 [thread overview]
Message-ID: <20080424164932.GB22233@2ka.mipt.ru> (raw)
In-Reply-To: <481096C3.2020206@redhat.com>
On Thu, Apr 24, 2008 at 07:18:43AM -0700, Ulrich Drepper (drepper@redhat.com) wrote:
> I don't think this is a viable approach because it is not about the
> range. People can and do select arbitrary values for those types.
> Until a value is officially recognized and registered it is in fact best
> to choose a (possibly large) random value to not conflict with anything
> else. Who can guarantee that whatever bit is chosen for SOCK_CLOEXEC
> isn't already used by someone?
type argument is limited to SOCK_MAX, higher half of the word can be
used for flags. It is much cleaner than implementing socket4() for the
single bit.
> Add to this that it's not a complete solution (no such hack possible for
> accept) and I think using a new interface is cleaner(tm).
It can inherit flags from parent by default.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-04-24 16:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 4:03 [PATCH] alternative to sys_indirect, part 1 Ulrich Drepper
2008-04-24 10:25 ` Alan Cox
2008-04-24 12:34 ` Michael Kerrisk
[not found] ` <517f3f820804240534r3bbbdc52s52a6dfe3f2d14b7f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-04-24 14:49 ` Ulrich Drepper
[not found] ` <48109DFB.900-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-04-24 14:42 ` Alan Cox
2008-04-24 15:19 ` Ulrich Drepper
2008-04-24 15:05 ` Michael Kerrisk
2008-04-24 14:18 ` Ulrich Drepper
2008-04-24 14:24 ` Alan Cox
2008-04-24 15:16 ` Ulrich Drepper
2008-04-24 15:03 ` Alan Cox
2008-04-24 15:44 ` Jakub Jelinek
2008-04-24 15:24 ` Alan Cox
2008-04-24 16:00 ` David Miller
2008-04-24 15:38 ` Alan Cox
2008-04-24 16:09 ` David Miller
2008-04-24 16:45 ` Michael Kerrisk
2008-04-26 22:41 ` dean gaudet
2008-04-24 15:45 ` Ulrich Drepper
2008-04-24 15:27 ` Alan Cox
2008-04-24 16:04 ` Ulrich Drepper
2008-04-24 15:45 ` Alan Cox
2008-04-24 16:06 ` Michael Kerrisk
2008-04-24 16:49 ` Evgeniy Polyakov [this message]
2008-04-24 15:29 ` Linus Torvalds
2008-04-24 15:39 ` David Miller
2008-04-24 16:03 ` Michael Kerrisk
2008-04-24 15:42 ` Alan Cox
2008-04-24 16:48 ` Michael Kerrisk
2008-04-24 17:20 ` H. Peter Anvin
2008-04-24 17:31 ` Ulrich Drepper
2008-04-24 17:34 ` H. Peter Anvin
2008-04-24 16:30 ` Linus Torvalds
2008-04-24 16:52 ` Ulrich Drepper
2008-04-24 12:27 ` Michael Kerrisk
2008-04-24 12:46 ` David Collier-Brown
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=20080424164932.GB22233@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).