From: Jens Axboe <jens.axboe@oracle.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [patch] pipe: add support for shrinking and growing pipes
Date: Thu, 20 May 2010 10:37:32 +0200 [thread overview]
Message-ID: <20100520083732.GI25951@kernel.dk> (raw)
In-Reply-To: <E1OF1C0-0007mV-VZ@pomaz-ex.szeredi.hu>
On Thu, May 20 2010, Miklos Szeredi wrote:
> On Wed, 19 May 2010, Jens Axboe wrote:
> > On Wed, May 19 2010, Jens Axboe wrote:
> > > On Wed, May 19 2010, Linus Torvalds 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.
> > >
> > > That's still a bit arbitrary, I don't think allowing default*2 only for
> > > non-root is going to be hugely interesting. But limiting makes sense,
> > > but lets at least allow a larger max limit for the normal user. I'm
> > > suspecting that the media application that wants to use this will not be
> > > running as root, and we don't make the feature properly available to the
> > > ones that want to use it, then we may as well not do it.
> > >
> > > Or we could expose a sysctl for instance that holds the max non-root
> > > size. And make that default to default*16 or something. How does that
> > > sound?
> > >
> > > > 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.
> > >
> > > Good point, and at least that part is easily doable :-)
> >
> > So I updated the patch, that branch was pretty ancient... The fcntl pipe
> > numbers were also screwed up, so got that fixed. New patch is here:
> >
> > http://git.kernel.dk/?p=linux-2.6-block.git;a=commit;h=23dcb845246946aeda5a5e398c6911381ad28365
>
> Not sure why you didn't take my updated patch. Yours misses
> conversion of kernel/trace/trace.c as well as some hunks below (that
> renaming the "pages" and "partial" arrays and a compile test would
> have revealed).
Sorry, I missed that you had done extra changes. I had to rebase the
whole thing anyway, and as I said it was totally untested. I'll get it
updated.
The main reason I didn't push it before is that I wasn't completely sure
that we wanted to use fcntl() for this. But Linus doesn't seem to object
on that side at least.
--
Jens Axboe
next prev parent reply other threads:[~2010-05-20 8:37 UTC|newest]
Thread overview: 57+ 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 [this message]
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
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
[not found] ` <4C07862D.4090709@fusionio.com>
[not found] ` <AANLkTincO5thcP-yASUtIV41TtY3ZmG9YSU-J5nT2sFg@mail.gmail.com>
2010-06-03 11:11 ` Jens Axboe
[not found] ` <4C078610.6020901@fusionio.com>
[not found] ` <AANLkTinhO5oRDPXyXaeAOZU3i55eBKsx4iFMOzwm98na@mail.gmail.com>
[not found] ` <AANLkTin_8MU3AbJ_KeXr2uTxtRFJ5ABmBAyigU6m-C6u@mail.gmail.com>
2010-06-03 11:12 ` Jens Axboe
2010-06-03 11:32 ` Miklos Szeredi
2010-06-03 11:37 ` Jens Axboe
2010-06-03 12:45 ` Miklos Szeredi
2010-06-03 12:50 ` Jens Axboe
2010-06-19 5:45 ` Michael Kerrisk
2010-06-19 18:13 ` Jens Axboe
2010-06-20 5:37 ` Michael Kerrisk
2010-06-03 16:06 ` Miklos Szeredi
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=20100520083732.GI25951@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--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).