From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>, X86 ML <x86@kernel.org>,
Network Development <netdev@vger.kernel.org>,
Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alexander Larsson <alexl@redhat.com>,
Cosimo Cecchi <cosimo@endlessm.com>,
Dan Nicholson <nicholson@endlessm.com>,
libc-alpha <libc-alpha@sourceware.org>,
Rajalakshmi Srinivasaraghavan <raji@linux.vnet.ibm.com>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] x86: Wire up 32-bit direct socket calls
Date: Mon, 14 Sep 2015 15:35:00 +0200 [thread overview]
Message-ID: <20150914133500.GA385@gmail.com> (raw)
In-Reply-To: <CALCETrVbNs-bOfr8cC3CC2RrBtKctdw4d0o9Ds6RQfXEm466YQ@mail.gmail.com>
* Andy Lutomirski <luto@amacapital.net> wrote:
> On Fri, Sep 11, 2015 at 3:14 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Friday 11 September 2015 11:54:50 Geert Uytterhoeven wrote:
> >> To make sure I don't miss any (it seems I missed recvmmsg and sendmmsg for
> >> the socketcall case, sigh), this is the list of ipc syscalls to implement?
> >>
> >> sys_msgget
> >> sys_msgctl
> >> sys_msgrcv
> >> sys_msgsnd
> >> sys_semget
> >> sys_semctl
> >> sys_semtimedop
> >> sys_shmget
> >> sys_shmctl
> >> sys_shmat
> >> sys_shmdt
> >>
> >> sys_semop() seems to be unneeded because it can be implemented using
> >> sys_semtimedop()?
> >>
> >
> > Yes, that list looks right. IPC also includes a set of six sys_mq_*
> > call, but I believe that everyone already has those as they are not
> > covered by sys_ipc.
> >
> > For y2038 compatibility, we will likely add a new variant of
> > semtimedop that takes a 64-bit timespec. While the argument passed
> > there is a relative time that will never need to be longer than 68
> > years, we need to accommodate user space that defines timespec
> > in a sane way, and converting the argument in libc would be awkward.
> >
>
> I missed sys_ipc entirely.
>
> Ingo, Thomas, want to just wire those up, too? I can send a patch
> next week, but it'll be as trivial as the socket one.
Yeah, sure - split out system calls are so much better (and slightly faster) than
omnibus demuxers.
Thanks,
Ingo
next prev parent reply other threads:[~2015-09-14 13:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cb5138299d37d5800e2d135b01a7667fa6115854.1436912629.git.luto@kernel.org>
2015-09-02 9:48 ` [PATCH] x86: Wire up 32-bit direct socket calls Geert Uytterhoeven
2015-09-02 20:16 ` H. Peter Anvin
2015-09-02 20:16 ` H. Peter Anvin
2015-09-03 10:06 ` David Laight
2015-09-03 10:06 ` David Laight
2015-09-07 12:53 ` Arnd Bergmann
2015-09-07 12:53 ` Arnd Bergmann
2015-09-11 8:24 ` Heiko Carstens
2015-09-11 8:24 ` Heiko Carstens
2015-09-11 8:46 ` Arnd Bergmann
2015-09-11 8:46 ` Arnd Bergmann
2015-09-11 9:54 ` Geert Uytterhoeven
2015-09-11 9:54 ` Geert Uytterhoeven
2015-09-11 10:14 ` Arnd Bergmann
2015-09-11 16:32 ` Andy Lutomirski
2015-09-11 16:32 ` Andy Lutomirski
2015-09-14 13:35 ` Ingo Molnar [this message]
2015-09-15 20:55 ` H. Peter Anvin
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=20150914133500.GA385@gmail.com \
--to=mingo@kernel.org \
--cc=alexl@redhat.com \
--cc=arnd@arndb.de \
--cc=cosimo@endlessm.com \
--cc=geert@linux-m68k.org \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicholson@endlessm.com \
--cc=raji@linux.vnet.ibm.com \
--cc=tuliom@linux.vnet.ibm.com \
--cc=x86@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).