From: David Miller <davem@davemloft.net>
To: benh@kernel.crashing.org
Cc: arnd@arndb.de, geert@linux-m68k.org, acme@redhat.com,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-m68k@vger.kernel.org
Subject: Re: sys_recvmmsg: wire up or not?
Date: Wed, 13 Jan 2010 20:28:07 -0800 (PST) [thread overview]
Message-ID: <20100113.202807.233259060.davem@davemloft.net> (raw)
In-Reply-To: <1263442833.724.325.camel@pasglop>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Thu, 14 Jan 2010 15:20:33 +1100
> Anything happening here ? We're getting that warning on ppc too despite
> the fact that we use socketcall like x86... Should checksyscall be made
> smarter or the syscall just removed from x86 ? :-)
I think it's better to trap directly to the system call rather
than going through yet another demultiplexer.
I severely regretted using sys_socketcall initially on sparc32
because it added a few microseconds to socket syscall latency
(cpus back then were slow :-)
next prev parent reply other threads:[~2010-01-14 4:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-26 10:39 sys_recvmmsg: wire up or not? Geert Uytterhoeven
2009-12-26 11:12 ` Arnd Bergmann
2010-01-14 4:20 ` Benjamin Herrenschmidt
2010-01-14 4:20 ` Benjamin Herrenschmidt
2010-01-14 4:28 ` David Miller [this message]
2010-01-14 6:59 ` Benjamin Herrenschmidt
2010-01-14 9:33 ` Russell King
2010-01-15 3:32 ` Benjamin Herrenschmidt
2010-01-19 7:21 ` Paul Mundt
2010-01-19 7:21 ` Paul Mundt
2010-01-19 23:14 ` Benjamin Herrenschmidt
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=20100113.202807.233259060.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=acme@redhat.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.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).