All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: David Miller <davem@davemloft.net>,
	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: Fri, 15 Jan 2010 14:32:49 +1100	[thread overview]
Message-ID: <1263526369.724.399.camel@pasglop> (raw)
In-Reply-To: <20100114093322.GA3484@flint.arm.linux.org.uk>

On Thu, 2010-01-14 at 09:33 +0000, Russell King wrote:
> On ARM, we used to use socketcall exclusively.  We've since added all
> the direct socket and IPC calls to our syscall table as part of the
> big EABI shakeup.  They certainly get used on EABI, whereas OABI has
> a choice.
> 
> They were made available in two stages - first the numbers were
> reserved
> and the calls were added to the call table.  A few years later, we
> exposed the syscall numbers in unistd.h.
> 
> It's now been almost 4 years since this was done, and there have been
> no bug reports. 

Agreed. It's definitely a switch we should do on powerpc. I'll look into
it after LCA.

Cheers,
Ben.

  reply	other threads:[~2010-01-15  3:34 UTC|newest]

Thread overview: 9+ 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:28     ` David Miller
2010-01-14  6:59       ` Benjamin Herrenschmidt
2010-01-14  9:33         ` Russell King
2010-01-15  3:32           ` Benjamin Herrenschmidt [this message]
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=1263526369.724.399.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=acme@redhat.com \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.