Date: Wed, 13 Jan 2010 20:28:07 -0800 (PST)
Message-Id: <20100113.202807.233259060.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?
From: David Miller <davem@davemloft.net>
In-Reply-To: <1263442833.724.325.camel@pasglop>
References: <10f740e80912260239n17bbbd08w6c3065c12bde9c95@mail.gmail.com>
	<200912261212.14264.arnd@arndb.de>
	<1263442833.724.325.camel@pasglop>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 807
Lines: 18

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 :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/