From: Andrew Morton <akpm@zip.com.au>
To: davidm@hpl.hp.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: maximum block size in buffer_head
Date: Thu, 09 May 2002 22:38:13 -0700 [thread overview]
Message-ID: <3CDB5CC5.2621C68C@zip.com.au> (raw)
In-Reply-To: <E1762h0-00086K-00@wailua.hpl.hp.com>
David Mosberger wrote:
>
> The current Linux kernel (both 2.4.xx and 2.5.xx) declare the b_size
> member in struct buffer_head as an "unsigned short". This obviously
> limits the maximum block size to something less than 65536. This is
> bad because on some platforms (e.g., ia64), the page size can be up to
> 64KB large.
>
> Two questions:
>
> - does anyone object to widening b_size to "unsigned int"?
Sounds OK to me for 2.5.
I do have vague plans to remove b_data and to replace all instances
with buffer_data(), which would kmap the page and calculate the address.
Not that I've really thought this through...
This may lead to the introduction of a `b_offset'. Which would be 16
bits, which would snuggle in with the 16-bit b_size. But I would
scale both these values by 256 or 512, for the reasons which you
identify.
For 2.4, a 32-bit b_size would push sizeof(buffer_head) from 96 up
to 100 bytes, which does not pack as well into the slab. This would
be an intensely unpopular move. So you'd have to ifdef it. Which
makes it an ia64-only problem, which greatly improves your merge
chances ;)
> - does anyone know of any other code paths where the block
> size is assumed to fit into 16 bits?
Not off the top, but they're probably there.
-
next prev parent reply other threads:[~2002-05-10 5:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 5:11 maximum block size in buffer_head David Mosberger
2002-05-10 5:38 ` Andrew Morton [this message]
2002-05-10 6:35 ` David Mosberger
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=3CDB5CC5.2621C68C@zip.com.au \
--to=akpm@zip.com.au \
--cc=davidm@hpl.hp.com \
--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