public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Licquia <licquia@progeny.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Fwd: Weird ia64 problem]
Date: Wed, 05 Oct 2005 23:09:46 +0000	[thread overview]
Message-ID: <1128553786.4623.83.camel@laptop1> (raw)
In-Reply-To: <1128548614.4623.45.camel@laptop1>

On Wed, 2005-10-05 at 15:33 -0700, Luck, Tony wrote:
> Running with a kernel configured for 4K pagesize, this
> test passes (prints "the write appeared to succeed").
> 
> I expect this difference in behavior can be traced to when
> Linus improved pipe performance by allowing a list of many
> pages to implement the pipe buffer.  See http://tinyurl.com/7jfen
> 
> The date on this is Jan 6th, 2005 ... which puts it between
> 2.6.10 and 2.6.11-rc1

This implies that PIPE_BUF should be equal to the kernel's configured
page size on ia64.  I modified my test to report on PIPE_BUF's returned
value, and it is 4096 on all my tested architectures, including ia64 on
2.6.8 and 2.6.12.

(Also, the page size on my 2.6.8 ia64 kernel is 16K, same as my 2.6.12
kernel.)

It strikes me that, if this is correct, forcing 4K page size isn't the
right fix.  Do you have any ideas on that front?


  parent reply	other threads:[~2005-10-05 23:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 21:43 [Fwd: Weird ia64 problem] Jeff Licquia
2005-10-05 21:54 ` Luck, Tony
2005-10-05 22:09 ` Luck, Tony
2005-10-05 22:13 ` Jeff Licquia
2005-10-05 22:30 ` Jeff Licquia
2005-10-05 22:33 ` Luck, Tony
2005-10-05 23:09 ` Jeff Licquia [this message]
2005-10-05 23:28 ` Luck, Tony
2005-10-05 23:40 ` Luck, Tony
2005-10-06  1:02 ` Ian Wienand
2005-10-07 14:29 ` Jeff Licquia
2005-10-08  2:40 ` Tony Luck

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=1128553786.4623.83.camel@laptop1 \
    --to=licquia@progeny.com \
    --cc=linux-ia64@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