From: Vadim Lobanov <vlobanov@speakeasy.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: limits / PIPE_BUF?
Date: Thu, 4 May 2006 10:50:43 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0605041044270.30003@shell2.speakeasy.net> (raw)
In-Reply-To: <1146762968.3101.65.camel@laptopd505.fenrus.org>
On Thu, 4 May 2006, Arjan van de Ven wrote:
> On Thu, 2006-05-04 at 09:39 -0700, Vadim Lobanov wrote:
> > How does the kernel
> > code ensure that this value is honored, considering that PIPE_BUF is
> > not
> > referenced in any of the pipe code?
>
>
> the kernel implementation guarantees one page basically, and on all
> architectures that I know of that's at least 4096 bytes
>
Alright, so sounds like this constant should remain inside the
include/linux/limits.h file. What about #defining it to be equal to
PAGE_SIZE, like ARM (include/linux-arm/limits.h, for example) does?
- Vadim Lobanov
next prev parent reply other threads:[~2006-05-04 17:50 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 [this message]
2006-05-04 17:54 ` Arjan van de Ven
2006-05-04 18:10 ` Vadim Lobanov
2006-05-04 7:15 ` Eric Piel
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=Pine.LNX.4.58.0605041044270.30003@shell2.speakeasy.net \
--to=vlobanov@speakeasy.net \
--cc=arjan@infradead.org \
--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®