From: willy@linux.intel.com (Matthew Wilcox)
Subject: LBA Range handling
Date: Thu, 24 Nov 2011 13:06:31 -0500 [thread overview]
Message-ID: <20111124180631.GD14291@linux.intel.com> (raw)
In-Reply-To: <5AC4D6A45304E048A30F105EB302760902CBB1D2@CORPEXCH1.na.ads.idt.com>
On Wed, Nov 23, 2011@01:47:20PM -0800, Kong, Kwok wrote:
> Actually, I am not sure how do use the LBA range. Who should set the
> LBA Range ? Should it be the driver or the application ? What should
> the driver behave if the type is 'page cache', 'RAID', 'Reserved' or
> 'FILESYSTEM' ?
>
> How are we supposed to use the LBA range ?
My understanding is that there will be a user-space application (like
fdisk) that will write the LBA Range Type attribute. The 'type' is
mostly for the benefit of this application and shouldn't be interpreted
by the driver.
prev parent reply other threads:[~2011-11-24 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 18:53 LBA Range handling Kong, Kwok
2011-11-23 21:34 ` Matthew Wilcox
2011-11-23 21:47 ` Kong, Kwok
2011-11-24 18:06 ` Matthew Wilcox [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=20111124180631.GD14291@linux.intel.com \
--to=willy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).