[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6D1CB8CE25@AcuExch.aculab.com>
Date: Thu, 3 Sep 2015 10:06:24 +0000
From: David Laight <David.Laight@...LAB.COM>
To: "'H. Peter Anvin'" <hpa@...or.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Andy Lutomirski <luto@...nel.org>
CC: X86 ML <x86@...nel.org>,
Network Development <netdev@...r.kernel.org>,
Tulio Magno Quites Machado Filho
<tuliom@...ux.vnet.ibm.com>, Andy Lutomirski <luto@...capital.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Alexander Larsson <alexl@...hat.com>,
Cosimo Cecchi <cosimo@...lessm.com>,
Dan Nicholson <nicholson@...lessm.com>,
libc-alpha <libc-alpha@...rceware.org>,
"Rajalakshmi Srinivasaraghavan" <raji@...ux.vnet.ibm.com>,
Linux-Arch <linux-arch@...r.kernel.org>
Subject: RE: [PATCH] x86: Wire up 32-bit direct socket calls
From: Peter Anvin
> Sent: 02 September 2015 21:16
> On 09/02/2015 02:48 AM, Geert Uytterhoeven wrote:
> >
> > Should all other architectures follow suit?
> > Or should we follow the s390 approach:
> >
>
> It is up to the maintainer(s), largely dependent on how likely you are
> going to want to support this in your libc, but in general, socketcall
> is an abomination which there is no reason not to bypass.
The other (worse) abomination is the way SCTP overloads setsockopt()
to perform actions that change state.
Rather unfortunately that got documented in the protocol standard :-(
David
Powered by blists - more mailing lists