From: Ad van den Broek <advandenbroek.nl@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: PIPE questions for Linux 2.4 setup
Date: Thu, 21 May 2009 16:56:36 +0200 [thread overview]
Message-ID: <9f924d250905210756l5db654abkf9c9fbc4170717ac@mail.gmail.com> (raw)
Dear C/Linux friends,
We wanted to increase PIPE_SIZE (from 4K to 8K on linux 2.4 on an AMD
LX800 system).
The result is a segmentation error as soon as Read() is reading more
data than 4K
from the pipe.
So pipe data seems to be damaged.
If we change PIPE_SIZE back tot 4K everything is running fine.
Question-1: Any suggestion to prevent this segmentation error ?
* PIPE_SIZE
If you look in the linux kernel code for PIPE_SIZE
("include/linux/pipe_fs_i.h") you find:
#define PIPE_SIZE PAGE_SIZE
I don't know if #define PIPE_SIZE PAGE_SIZE is necessary or just a
simple shortcut.
Question-2: Is it OK if PIPE_SIZE > PAGE_SIZE ?
* PAGE_SIZE
Question-3: Is it OK to increase Page_size on linux 2.4 on AMD LX800 system ?
Which aspects are limiting the user to config the PAGE_SIZE ?
--
With best regards,
Ad van den Broek
next reply other threads:[~2009-05-21 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 14:56 Ad van den Broek [this message]
2009-05-21 19:51 ` PIPE questions for Linux 2.4 setup Glynn Clements
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=9f924d250905210756l5db654abkf9c9fbc4170717ac@mail.gmail.com \
--to=advandenbroek.nl@gmail.com \
--cc=linux-c-programming@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).