From: Rik van Riel <riel@redhat.com>
To: "Fausto Richetti Blanco" <fausto.blanco@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Pipe buffers' limit of 16 * 4K
Date: Fri, 23 May 2008 20:56:30 -0400 [thread overview]
Message-ID: <20080523205630.444fe2b9@bree.surriel.com> (raw)
In-Reply-To: <d8d698ae0805231719g4202edf2k947bba4128385ab6@mail.gmail.com>
On Fri, 23 May 2008 21:19:13 -0300
"Fausto Richetti Blanco" <fausto.blanco@gmail.com> wrote:
> Hello guys,
>
> I'm working with a 2.6.9 kernel (ok, I know it's quite old) and
> faced a problem with the 4K (one page) buffer limit for the pipes.
> I've found that in the 2.6.11 the pipes' buffers were changed to a
> circular list of pages which increased this limit to 16 * 4K. This
> limit is hardcoded here /usr/src/linux/include/linux/pipe_fs_i.h:6
> #define PIPE_BUFFERS (16)
>
> Is there a reason for this not to be an adjustable parameter
> (eg.: by an ulimit in the userspace) ?
What is the problem you found?
Why do you need to change the limit from 16?
Did it bring you any performance enhancements?
If so, how much?
--
All rights reversed.
next prev parent reply other threads:[~2008-05-24 0:56 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 ` Fausto Richetti Blanco
2008-05-24 0:56 ` Rik van Riel [this message]
[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
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=20080523205630.444fe2b9@bree.surriel.com \
--to=riel@redhat.com \
--cc=fausto.blanco@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®