From: David Woodhouse <dwmw2@infradead.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
akpm@osdl.org
Subject: Re: Add pselect, ppoll system calls.
Date: Mon, 13 Jun 2005 17:02:27 +0100 [thread overview]
Message-ID: <1118678548.25956.200.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <42ADA880.60303@redhat.com>
On Mon, 2005-06-13 at 08:38 -0700, Ulrich Drepper wrote:
> And change it to expect a 64bit value I hope...
64-bit value for which? For seconds? Do we need to support timeouts of
longer than 4 milliard seconds? We can't currently come close to that
anyway -- we're limited to LONG_MAX / HZ seconds, and if the user asks
for more than that then it appears to be silently switched to an
infinite timeout.
> As long as there is a configuration where the timeout value is not
> modified, it doesn't matter. That is the case for select() using a
> personality switch.
I think it would be best to behave likewise for pselect().
--
dwmw2
next prev parent reply other threads:[~2005-06-13 16:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 22:58 David Woodhouse
2005-06-12 22:48 ` Alan Cox
2005-06-13 0:26 ` Linus Torvalds
2005-06-13 1:16 ` jnf
2005-06-13 3:26 ` Linus Torvalds
2005-06-13 6:22 ` Ulrich Drepper
2005-06-13 9:16 ` bert hubert
2005-06-13 9:41 ` David Woodhouse
2005-06-13 11:05 ` Christoph Hellwig
2005-06-13 11:14 ` Jakub Jelinek
2005-06-13 11:24 ` David Woodhouse
2005-06-13 15:38 ` Ulrich Drepper
2005-06-13 16:02 ` David Woodhouse [this message]
2005-06-13 16:10 ` Ulrich Drepper
2005-06-13 16:29 ` David Woodhouse
2005-06-13 16:31 ` Ulrich Drepper
2005-06-13 21:58 ` David Woodhouse
2005-06-13 22:01 ` Ulrich Drepper
2005-06-13 16:36 ` Jakub Jelinek
2005-06-15 11:36 ` David Woodhouse
2005-08-05 10:42 ` pselect() modifying timeout Michael Kerrisk
2005-08-05 14:50 ` Ulrich Drepper
2005-08-05 20:08 ` Michael Kerrisk
2005-08-08 11:10 ` Alan Cox
2005-08-05 11:58 ` Add pselect, ppoll system calls Michael Kerrisk
2005-08-05 12:49 ` Michael Kerrisk
2005-08-25 0:04 ` David Woodhouse
2005-08-25 0:34 ` Ulrich Drepper
2005-08-26 6:46 ` Michael Kerrisk
2005-06-13 15:35 ` Ulrich Drepper
2005-06-13 7:23 ` Benjamin Herrenschmidt
2005-06-13 7:29 ` David Woodhouse
2005-06-13 22:56 ` Benjamin Herrenschmidt
2005-06-13 11:15 ` Alan Cox
2005-06-13 11:27 ` David Woodhouse
2005-06-13 15:40 ` Ulrich Drepper
2005-06-13 19:38 Mattias Engdegård
2005-06-13 19:57 ` Chris Friesen
2005-06-13 20:08 ` Mattias Engdegård
2005-06-13 20:23 ` Valdis.Kletnieks
2005-06-14 14:07 ` Mattias Engdegård
2005-06-14 14:16 ` Bernd Petrovitsch
2005-06-14 14:42 ` Mattias Engdegård
2005-06-14 14:54 ` Bernd Petrovitsch
2005-06-14 15:27 ` Valdis.Kletnieks
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=1118678548.25956.200.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®