From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Davide Libenzi <davidel@xmailserver.org>,
Ulrich Drepper <drepper@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, mtk.manpages@gmail.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 02/18] flag parameters: socket and socketpair
Date: Tue, 6 May 2008 12:43:15 +0100 [thread overview]
Message-ID: <20080506124315.4567ee73@core> (raw)
In-Reply-To: <20080505191725.89faed88.akpm@linux-foundation.org>
> > > type = flag_remap(type, &fflags, SOCK_whatever, O_whatever);
> > > type = flag_remap(type, &fflags, SOCK_whatever2, O_whatever2);
> > >
> > > ?
> >
> > I think it is better to keep it able to remap more than one flag, with a
> > single call, that is table driven.
> >
>
> The table-driven approach is slower for one and probably two bits and it is
> somewhat less readable. What do we gain in return for this?
Acute over-engineering ?
We've got lots of space for flag bits so surely we can do remap with a
shift and mask.
flags = (type >> SOCK_FLAG_SHIFT) & SOCK_FLAG_MASK;
type = type & SOCK_TYPE_MASK
For most boxes
SOCK_TYPE_MASK can easily be 0xFF
SOCK_FLAG_MASK O_CLOEXEC
SOCK_FLAG_SHIFT 0
and tweaked a bit depending what other flags we want.
In Linux we could actually just do SOCK_STREAM|O_CLOEXEC but that would be
bad news for portability to other OS where the trick might well not work.
next prev parent reply other threads:[~2008-05-06 11:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 3:42 [PATCH 02/18] flag parameters: socket and socketpair Ulrich Drepper
2008-05-05 4:24 ` YOSHIFUJI Hideaki / 吉藤英明
2008-05-05 5:00 ` Ulrich Drepper
2008-05-05 8:11 ` David Miller
2008-05-06 1:58 ` Andrew Morton
2008-05-06 2:13 ` Davide Libenzi
2008-05-06 2:17 ` Andrew Morton
2008-05-06 2:30 ` Davide Libenzi
2008-05-06 11:43 ` Alan Cox [this message]
2008-05-06 2:33 ` Ulrich Drepper
2008-05-06 2:42 ` Andrew Morton
2008-05-06 2:58 ` Ulrich Drepper
2008-05-06 3:05 ` Andrew Morton
2008-05-06 3:10 ` Ulrich Drepper
2008-05-06 3:02 ` Ulrich Drepper
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=20080506124315.4567ee73@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--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).