From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: blocks or KB? (was: .. current meaning of blk_size array)
Date: Tue, 13 Nov 2001 19:51:29 +0100 (MET) [thread overview]
Message-ID: <200111131851.fADIpTN20263@oboe.it.uc3m.es> (raw)
In-Reply-To: <200111131508.fADF8Yi09728@oboe.it.uc3m.es> from "Peter T. Breuer" at "Nov 13, 2001 04:08:34 pm"
Let me put it more plainly. Martin Daleki + rumour assures me that the
blk_size array nowadays measure in blocks not KB, yet to me it seems that
it doesn't. Look at this code from ll_rw_blk.c in 2.4.13:
unsigned long maxsector = (blk_size[major][MINOR(bh->b_rdev)] << 1) + 1;
and this comment:
* blk_size contains the size of all block-devices in units of 1024
* byte sectors:
so blk_size measures in KB. Where do I see it wrong? Is everybody
talking about 2.4.14 and 2.4.15? No .. it's just the same in 2.4.14:
if (blk_size[major])
minorsize = blk_size[major][MINOR(bh->b_rdev)];
if (minorsize) {
unsigned long maxsector = (minorsize << 1) + 1;
KB! Or is it the case that sectors don't mean 512B?
Peter
next prev parent reply other threads:[~2001-11-13 18:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 15:08 what is teh current meaning of blk_size? Peter T. Breuer
2001-11-13 18:51 ` Peter T. Breuer [this message]
2001-11-14 9:44 ` blocks or KB? (was: .. current meaning of blk_size array) Martin Dalecki
2001-11-14 20:41 ` Peter T. Breuer
2001-11-14 20:51 ` Martin Dalecki
2001-11-14 21:16 ` Andreas Dilger
2001-11-14 21:49 ` Benjamin LaHaise
2001-11-14 22:33 ` Scott Laird
2001-11-15 1:48 ` William Park
2001-11-15 4:58 ` Andreas Dilger
2001-11-15 5:34 ` William Park
2001-11-15 5:55 ` Andreas Dilger
2001-11-15 12:35 ` Peter T. Breuer
2001-11-15 18:31 ` William Park
2001-11-15 20:19 ` Andreas Dilger
2001-11-15 22:04 ` blocks or KB? William Park
2001-11-15 10:42 ` blocks or KB? (was: .. current meaning of blk_size array) Anton Altaparmakov
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=200111131851.fADIpTN20263@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--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®