public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miquel van Smoorenburg <miquels@cistron.nl>
To: Fausto Richetti Blanco <fausto.blanco@gmail.com>
Cc: linux-kernel@vger.kernel.org, riel@redhat.com, jengelh@medozas.de
Subject: Re: Pipe buffers' limit of 16 * 4K
Date: Thu, 29 May 2008 15:19:24 +0200	[thread overview]
Message-ID: <1212067164.8621.3.camel@localhost.localdomain> (raw)
In-Reply-To: <d8d698ae0805290600s782e16b4pe70d725f55826cf0@mail.gmail.com>

On Thu, 2008-05-29 at 10:00 -0300, Fausto Richetti Blanco wrote:
> Yes, I need an unspecified amount (it is the data content of a HTTP POST).
> 
> The tee system call appeared in the 2.6.17 (I'm using 2.6.9). That's
> because I did my implementation using a buffer and copying it using
> write. Unfortunately, both solutions suffer from the kernel buffer
> limitation.
> 
> As I said, there's a lot of other solutions to my specific problem.
> I'll problably move my solution inside the lib =/ But I decided to
> write to this list to ask for dynamically adjustable sizes for the
> pipes' buffers. Is there any good reason for this not to be pushed to
> the kernel head ?

Why not use a socketpair() instead of a pipe(). You can adjust the size
with setsockopt SO_SNDBUF/SO_RCVBUF (see man socket(7))

Mike.


  reply	other threads:[~2008-05-29 13:20 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 [this message]
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=1212067164.8621.3.camel@localhost.localdomain \
    --to=miquels@cistron.nl \
    --cc=fausto.blanco@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox