From: David Miller <davem@davemloft.net>
To: jamie@shareable.org
Cc: tony.luck@intel.com, linux-arch@vger.kernel.org
Subject: Re: why doesn't x86_32 have the accept4() syscall?
Date: Tue, 10 Jan 2012 12:07:24 -0800 (PST) [thread overview]
Message-ID: <20120110.120724.178373558788579377.davem@davemloft.net> (raw)
In-Reply-To: <20120110160317.GC7180@jl-vm1.vm.bytemark.co.uk>
From: Jamie Lokier <jamie@shareable.org>
Date: Tue, 10 Jan 2012 16:03:17 +0000
> Is there any reason why it was added via sys_socketcall() - isn't that
> just a waste of a few cycles and kernel size, compared with a direct
> pointer in the syscall table?
Looks like an oversight, but one for which I don't think is worth
correcting.
next prev parent reply other threads:[~2012-01-10 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 21:26 why doesn't x86_32 have the accept4() syscall? Tony Luck
2012-01-09 21:36 ` David Miller
2012-01-10 16:03 ` Jamie Lokier
2012-01-10 17:00 ` Geert Uytterhoeven
2012-01-10 20:07 ` David Miller [this message]
2012-01-12 0:33 ` Michael Cree
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=20120110.120724.178373558788579377.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jamie@shareable.org \
--cc=linux-arch@vger.kernel.org \
--cc=tony.luck@intel.com \
/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).