From: Randy Dunlap <rdunlap@xenotime.net>
To: Roger Gammans <roger@computer-surgery.co.uk>
Cc: lkml <linux-kernel@vger.kernel.org>, axboe@kernel.dk
Subject: Re: fs/bio.c - Hardcoded sector size ?
Date: Fri, 29 Sep 2006 13:17:30 -0700 [thread overview]
Message-ID: <20060929131730.0b733137.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060928195627.GD4759@julia.computer-surgery.co.uk>
On Thu, 28 Sep 2006 20:56:27 +0100 Roger Gammans wrote:
> On Fri, Sep 29, 2006 at 12:37:37PM -0700, Randy Dunlap wrote:
> > Hm, I looked thru fs/bio.c and block/*.c and Documentation/Docbook/*.tmpl.
> > The best place that I see to put it right now is in
> > include/linux/bio.h, struct bio, field: bi_sector.
> >
> > What do you think of that?
>
> Well, ... Um. I can't think of anywhere better either, so how about
> this:-
>
> Signed-Off-By: Roger Gammans <rgammans@computer-sugery.co.uk>
Looks OK to me. I would probably go for something a little
stronger, though, like:
sector_t bi_sector; /* block layer sector
* addresses are always in
* 512-byte units in Linux */
Jens, is something like this (above or below) OK with you?
> diff --git a/include/linux/bio.h b/include/linux/bio.h
> index 76bdaea..77a8e6b 100644
> --- a/include/linux/bio.h
> +++ b/include/linux/bio.h
> @@ -70,7 +70,8 @@ typedef void (bio_destructor_t) (struct
> * stacking drivers)
> */
> struct bio {
> - sector_t bi_sector;
> + sector_t bi_sector; /* device address in 512 byte
> + sectors */
> struct bio *bi_next; /* request queue link */
> struct block_device *bi_bdev;
> unsigned long bi_flags; /* status, command, etc
> */
---
~Randy
next prev parent reply other threads:[~2006-09-29 20:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 18:22 Roger Gammans
2006-09-29 18:38 ` Randy Dunlap
2006-09-28 18:58 ` linux-kernel-owner
2006-09-29 19:11 ` Randy Dunlap
2006-09-28 19:19 ` Roger Gammans
2006-09-29 19:37 ` Randy Dunlap
2006-09-28 19:56 ` Roger Gammans
2006-09-29 20:17 ` Randy Dunlap [this message]
2006-09-29 20:22 ` Zach Brown
2006-09-29 20:32 ` Randy Dunlap
2006-09-29 17:25 ` Roger Gammans
2006-09-30 19:31 ` Jens Axboe
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=20060929131730.0b733137.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=roger@computer-surgery.co.uk \
/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®