public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Aboo Valappil <aboo@aboo.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: About SG Elements of request_buffer
Date: Sun, 15 Oct 2006 10:53:59 -0500	[thread overview]
Message-ID: <1160927640.3544.2.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <453223AA.50409@aboo.org>

On Sun, 2006-10-15 at 22:03 +1000, Aboo Valappil wrote:
> 1. Is it safe to assume that all the SG elements of request_buffer are 
> page aligned? (Except the first one and last one),  I mean, it is always 
> multiple of pages?

No.

It's an artifact of block sector size >= PAGE_SIZE and the access method
only using pages.  It isn't even true of ext3 which does its metadata
through the buffer cache.

James



  parent reply	other threads:[~2006-10-15 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-15 12:03 About SG Elements of request_buffer Aboo Valappil
2006-10-15 15:40 ` Douglas Gilbert
2006-10-15 15:53 ` James Bottomley [this message]
2006-10-25  9:05 ` Aboo Valappil

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=1160927640.3544.2.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@steeleye.com \
    --cc=aboo@aboo.org \
    --cc=linux-scsi@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