From: Paul Menage <pmenage@ensim.com>
To: Ryan Anderson <ryan@michonline.com>
Cc: linux-kernel@vger.kernel.org
Cc: pmenage@ensim.com
Subject: Re: manipulating sigmask from filesystems and drivers
Date: Fri, 02 Aug 2002 16:30:12 -0700 [thread overview]
Message-ID: <E17als4-00048R-00@pmenage-dt.ensim.com> (raw)
In-Reply-To: Your message of "Fri, 02 Aug 2002 19:25:01 EDT." <Pine.LNX.4.10.10208021920210.579-100000@mythical.michonline.com>
>> How about a sysctl that lets the user specify the size threshold at
>> which writes use a killable wait state rather than
>> TASK_UNINTERRUPTIBLE? (Probably defaulting to never.)
>
>/usr/include/linux/limits.h:#define PIPE_BUF 4096 /* #
>bytes in atomic write to a pipe */
>
>According to SUSv3, this is the maximum size that write is guaranteed to
>be atomic for.
But that doesn't mean that we can't allow the user to configure higher
limits if they're using some particular software that relies on (and
more importantly, has successfully relied upon in the past) the current
behaviour of no interruptions.
Paul
next prev parent reply other threads:[~2002-08-02 23:26 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0C01A29FBAE24448A792F5C68F5EA47D2D3E2B@nasdaq.ms.ensim.com>
2002-08-02 17:57 ` Paul Menage
2002-08-02 23:25 ` Ryan Anderson
2002-08-02 23:30 ` Paul Menage [this message]
2002-08-02 18:24 Jesse Pollard
-- strict thread matches above, loose matches on Subject: below --
2002-07-31 11:52 David Howells
2002-07-31 11:58 ` Alan Cox
2002-08-01 19:09 ` Linus Torvalds
2002-08-01 20:10 ` David Woodhouse
2002-08-01 20:21 ` Linus Torvalds
2002-08-01 20:47 ` Roman Zippel
2002-08-01 20:51 ` Linus Torvalds
2002-08-01 21:15 ` Roman Zippel
2002-08-01 21:42 ` Linus Torvalds
2002-08-01 22:29 ` David Woodhouse
2002-08-01 22:40 ` Linus Torvalds
2002-08-01 22:50 ` David Woodhouse
2002-08-02 15:59 ` yodaiken
2002-08-01 22:35 ` Roman Zippel
2002-08-01 23:30 ` Linus Torvalds
2002-08-02 0:31 ` Olivier Galibert
2002-08-02 8:00 ` Kai Henningsen
2002-08-02 10:02 ` Roman Zippel
2002-08-02 12:38 ` Ryan Anderson
2002-08-02 15:39 ` Linus Torvalds
2002-08-02 16:00 ` Benjamin LaHaise
2002-08-02 16:27 ` Linus Torvalds
2002-08-02 17:13 ` Jamie Lokier
2002-08-02 17:29 ` Linus Torvalds
2002-08-02 17:57 ` Trond Myklebust
2002-08-02 18:10 ` Linus Torvalds
2002-08-02 17:33 ` Oliver Neukum
2002-08-03 18:27 ` David Woodhouse
2002-10-17 8:32 ` David Woodhouse
2002-08-02 19:27 ` Roman Zippel
2002-08-02 7:31 ` Giuliano Pochini
[not found] ` <mailman.1028232841.11555.linux-kernel2news@redhat.com>
2002-08-01 23:37 ` Pete Zaitcev
2002-08-01 23:46 ` David Woodhouse
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=E17als4-00048R-00@pmenage-dt.ensim.com \
--to=pmenage@ensim.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan@michonline.com \
/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®