Re: manipulating sigmask from filesystems and drivers

From: Paul Menage (
Date: Fri Aug 02 2002 - 18:30:12 EST

>> 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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:21 EST