From: William Lee Irwin III <wli@holomorphy.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Zwane Mwaikambo <zwane@holomorphy.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: RPCSVC_MAXPAGES doesn't account for overhead(?) pages
Date: Sun, 23 Mar 2003 03:42:39 -0800 [thread overview]
Message-ID: <20030323114239.GF30140@holomorphy.com> (raw)
In-Reply-To: <shs7kaqz5y6.fsf@charged.uio.no>
" " == Zwane Mwaikambo <zwane@holomorphy.com> writes:
>> -#define RPCSVC_MAXPAGES
>> ((RPCSVC_MAXPAYLOAD+PAGE_SIZE-1)/PAGE_SIZE + 1) + +#define
>> RPCSVC_MAXPAGES
>> (2+((RPCSVC_MAXPAYLOAD+PAGE_SIZE-1)/PAGE_SIZE+1))
On Sun, Mar 23, 2003 at 12:18:57PM +0100, Trond Myklebust wrote:
> Huh? RPCSVC_MAXPAYLOAD is set at 64k. Should be quite ample for a 32k
> read or write.
Sure, there's just a dependency on PAGE_SIZE we're trying to get sorted
out here. If PAGE_SIZE is 64KB (e.g. IA64, pgcl) then this trips a BUG().
-- wli
prev parent reply other threads:[~2003-03-23 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 16:46 RPCSVC_MAXPAGES doesn't account for overhead(?) pages Zwane Mwaikambo
2003-03-22 16:52 ` Zwane Mwaikambo
2003-03-22 17:11 ` William Lee Irwin III
2003-03-23 11:18 ` Trond Myklebust
2003-03-23 11:42 ` William Lee Irwin III [this message]
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=20030323114239.GF30140@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--cc=zwane@holomorphy.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