[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200805050054.20903.arnd@arndb.de>
Date: Mon, 5 May 2008 00:54:19 +0200
From: Arnd Bergmann <arnd@...db.de>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: monstr@...nam.cz, microblaze-uclinux@...e.uq.edu.au,
Matthew Wilcox <matthew@....cx>,
Will Newton <will.newton@...il.com>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
linux-arch@...r.kernel.org, git@...inx.com,
John Williams <john.williams@...alogix.com>,
Stephen Neuendorffer <stephen.neuendorffer@...inx.com>,
John Linn <John.Linn@...inx.com>
Subject: Re: microblaze syscall list
On Monday 05 May 2008, H. Peter Anvin wrote:
> Michal Simek wrote:
> > /* fs/select.c */
> > .long sys_select /* obsolete -> sys_pselect6 */
> > ok .long sys_pselect7
> > .long sys_pselect6 /* obsolete -> sys_pselect7 */
>
> I thought there was some semantic differences between select() and
> pselect()... perhaps those changes have been removed?
According to the main page, there are three differences:
* POSIX pselect does not update the timeout argument, but linux pselect7
does, so it's easy to implement both pselect and select based on it.
* pselect also has a timespec arguement, not timeval as select, but that's
trivial to convert.
* pselect obviously takes an extra argument, but if that's NULL, it will
behave like select (aside from the timeout handling).
Arnd <><
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists