From: Michael Kerrisk <mtk.manpages@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
jens.axboe@oracle.com, akpm@linux-foundation.org,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [patch] pipe: add support for shrinking and growing pipes
Date: Sun, 23 May 2010 07:30:01 +0200 [thread overview]
Message-ID: <AANLkTikkRywJSJ8HFsVhVU9dHz8cFGqlK9ZHXZuGQbb2@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1005190946540.23538@i5.linux-foundation.org>
Hi all,
I see that this patch has hit Linus's git, so some questions
On Wed, May 19, 2010 at 6:49 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
>
> On Wed, 19 May 2010, Miklos Szeredi wrote:
>>
>> One issue I see is that it's possible to grow pipes indefinitely.
>> Should this be restricted to privileged users?
>
> Yes. But perhaps only if it grows past the default (or perhaps "default*2"
> or similar). That way a normal user could shrink the pipe buffers, and
> then grow them again if he wants to.
>
> Oh, and I think you need to also require that there be at least two
> buffers. Otherwise we can't guarantee POSIX behavior, I think.
Is there any documentation (e.g., a man-pages patch) for these changes?
The argument of the fcntl() operations is expressed in pages. I take
it that this means that the semantics of the argument will very
depending on the system page size? So for example, 2 on x86 will mean
8192 bytes, but will mean 32768 of ia64? That seems very weird. (And
what about architectures where the page size is switchable?) Such
changes in semantics should not be silent for the use, IMO.
I'm not so sure about Linus's assertion above about needing at least
two buffers (pages?) to guarantee POSIX behavior. Back in 2.16.10 and
earlier, the buffer size was a page (4096 bytes) on x86-32, and we had
POSIX-compliant behavior.
Cheers,
Michael
--
Michael Kerrisk Linux man-pages maintainer;
http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface", http://blog.man7.org/
next prev parent reply other threads:[~2010-05-23 5:30 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 16:45 [patch] pipe: add support for shrinking and growing pipes Miklos Szeredi
2010-05-19 16:49 ` Linus Torvalds
2010-05-19 18:05 ` Jens Axboe
2010-05-19 19:05 ` Jens Axboe
2010-05-20 8:33 ` Miklos Szeredi
2010-05-20 8:37 ` Jens Axboe
2010-05-20 17:42 ` Linus Torvalds
2010-05-20 17:48 ` Jens Axboe
2010-05-21 17:13 ` Rick Sherm
2010-05-23 5:30 ` Michael Kerrisk [this message]
2010-05-23 2:38 ` Andrew Morton
2010-05-23 5:52 ` Michael Kerrisk
2010-05-23 7:09 ` Jens Axboe
2010-05-23 9:24 ` Michael Kerrisk
2010-05-23 17:47 ` Jens Axboe
2010-05-24 1:43 ` OGAWA Hirofumi
2010-05-24 4:43 ` Michael Kerrisk
2010-05-24 7:05 ` Jens Axboe
2010-05-24 7:27 ` Michael Kerrisk
2010-05-24 17:35 ` Jens Axboe
2010-05-24 17:52 ` Michael Kerrisk
2010-05-24 17:56 ` Jens Axboe
2010-05-25 4:01 ` Michael Kerrisk
2010-06-01 7:48 ` Jens Axboe
2010-06-01 15:22 ` Linus Torvalds
2010-06-01 16:36 ` Loke, Chetan
2010-05-27 6:49 ` Michael Kerrisk
2010-06-01 7:45 ` Jens Axboe
2010-06-02 19:25 ` Michael Kerrisk
2010-06-03 6:10 ` Jens Axboe
2010-06-03 6:46 ` Michael Kerrisk
2010-06-03 7:01 ` Jens Axboe
2010-06-03 7:05 ` Michael Kerrisk
2010-06-03 7:48 ` Michael Kerrisk
2010-06-03 7:58 ` Michael Kerrisk
2010-06-03 8:29 ` Michael Kerrisk
2010-06-03 8:53 ` Michael Kerrisk
2010-05-24 7:04 ` Jens Axboe
2010-05-24 7:28 ` Michael Kerrisk
2010-05-24 7:49 ` OGAWA Hirofumi
2010-05-24 14:51 ` Brian Bloniarz
2010-05-24 15:43 ` Michael Kerrisk
2010-05-24 7:46 ` OGAWA Hirofumi
2010-05-24 17:15 ` Jens Axboe
2010-05-24 18:12 ` OGAWA Hirofumi
2010-05-24 18:16 ` Michael Kerrisk
2010-05-20 12:52 ` Andi Kleen
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=AANLkTikkRywJSJ8HFsVhVU9dHz8cFGqlK9ZHXZuGQbb2@mail.gmail.com \
--to=mtk.manpages@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.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).