From: Eric Piel <Eric.Piel@tremplin-utc.net>
To: Vadim Lobanov <vlobanov@speakeasy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: limits / PIPE_BUF?
Date: Thu, 04 May 2006 09:15:39 +0200 [thread overview]
Message-ID: <4459AA1B.9020207@tremplin-utc.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0605032244230.25908@shell2.speakeasy.net>
05/04/2006 07:55 AM, Vadim Lobanov wrote/a écrit:
> Hi,
Hi!
:
>
> A snippet from include/linux/limits.h:
> #define PIPE_BUF 4096 /* # bytes in atomic write to a pipe */
>
> PIPE_BUF is a bit of an oddity. It is defined there, then redefined in
> the arm header files, even though those header files are never included
> anywhere.
Actually, here, on a 2.6.16 source code, PIPE_BUF is used in
arch/sparc/kernel/sys_sunos.c, arch/sparc64/kernel/sys_sunos32.c, and
arch/sparc64/solaris/fs.c . It seems it's some kind of compatibility
value with Sun's OS...
> Also, PIPE_BUF is never referenced by name in any of the Linux
> code. And yet, it is still being mentioned in some Big And Scary
> Warnings (tm): fs/autofs4/waitq.c or include/linux/pipe_fs_i.h, for
> example.
Maybe they wanted to say PIPE_BUFFERS ? (just wild guess)
c u,
Eric
next prev parent reply other threads:[~2006-05-04 7:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 5:55 Vadim Lobanov
2006-05-04 6:58 ` Arjan van de Ven
2006-05-04 16:39 ` Vadim Lobanov
2006-05-04 17:16 ` Arjan van de Ven
2006-05-04 17:50 ` Vadim Lobanov
2006-05-04 17:54 ` Arjan van de Ven
2006-05-04 18:10 ` Vadim Lobanov
2006-05-04 7:15 ` Eric Piel [this message]
2006-05-04 16:42 ` Vadim Lobanov
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=4459AA1B.9020207@tremplin-utc.net \
--to=eric.piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vlobanov@speakeasy.net \
/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®