From: Jens Axboe <jens.axboe@oracle.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Fausto Richetti Blanco <fausto.blanco@gmail.com>,
linux-kernel@vger.kernel.org, miquels@cistron.nl,
riel@redhat.com
Subject: Re: Pipe buffers' limit of 16 * 4K
Date: Fri, 6 Jun 2008 11:19:17 +0200 [thread overview]
Message-ID: <20080606091916.GM5757@kernel.dk> (raw)
In-Reply-To: <alpine.LNX.1.10.0806051155070.29055@fbirervta.pbzchgretzou.qr>
On Thu, Jun 05 2008, Jan Engelhardt wrote:
>
> On Friday 2008-05-30 12:35, Jens Axboe wrote:
> >
> >I have an old patch that does that, I just looked it up and it was last
> >updated for 2.6.23. It uses fcntl() with F_SETPIPE_SZ for getting and
> >setting the pipe size.
> >
> >Patch updated, the below is the current Linus kernel.
>
> Can you merge it?
I could, but I think two key things are missing:
- Is fcntl() the interface we want for changing the pipe size?
- So far, no real problems or performance increases have been
demonstrated.
I'd rather not attempt to push this until the two things have been
addressed/discussed.
--
Jens Axboe
next prev parent reply other threads:[~2008-06-06 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d8d698ae0805231255i4d0da724p68cb2b9376134797@mail.gmail.com>
2008-05-24 0:19 ` Pipe buffers' limit of 16 * 4K Fausto Richetti Blanco
2008-05-24 0:56 ` Rik van Riel
[not found] ` <d8d698ae0805261043u125b653ve73d067cd92caa16@mail.gmail.com>
2008-05-28 21:22 ` Fausto Richetti Blanco
2008-05-28 22:05 ` Jan Engelhardt
2008-05-29 13:00 ` Fausto Richetti Blanco
2008-05-29 13:19 ` Miquel van Smoorenburg
2008-05-29 14:36 ` Jan Engelhardt
2008-05-29 15:46 ` Fausto Richetti Blanco
2008-05-30 10:35 ` Jens Axboe
2008-06-05 9:55 ` Jan Engelhardt
2008-06-06 9:19 ` Jens Axboe [this message]
2008-05-26 14:15 ` Jan Engelhardt
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=20080606091916.GM5757@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=fausto.blanco@gmail.com \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
--cc=riel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.