From: Tejun Heo <tj@kernel.org>
To: Konrad Rzeszutek <konrad@virtualiron.com>
Cc: jens.axboe@oracle.com, jeff@garzik.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
martin.petersen@oracle.com, linux-ide@vger.kernel.org,
device-mapper development <dm-devel@redhat.com>,
Mauelshagen@redhat.com
Subject: Re: Re: [PATCH 1/3] block: add alt_size
Date: Tue, 12 May 2009 09:53:05 +0900 [thread overview]
Message-ID: <4A08C871.9000100@kernel.org> (raw)
In-Reply-To: <20090511134534.GA32678@mars.virtualiron.com>
Konrad Rzeszutek wrote:
> .. snip ..
>>> Also, values with magic block counts, while there is no way to get the
>>> blocksize with the same interface, are pretty weird. I think the
>>> current "size" attribute is just a bug.
>> Logical block size is fixed at 512 bytes. Offset and size are always
>> represented in multiples of 512 bytes and only get converted to
>> hardware block size in the lld.
>
> That interpretation is at odds with the work that Martin Peterson is
> doing with the 4K support. In the e-mail titled: "Re: [PATCH 4 of 8] sd:
> Physical block size and alignment support",
> Message-ID:<yq1ab67b51p.fsf@sermon.lab.mkp.net> he says:
>
> "
> Konrad> about what a 'logical block', and 'physical block' is
> Konrad> vs. 'hardware sector' ?
>
> Well, another item on my todo list is to kill the notion of hardware
> sector completely. The protocols have been referring to logical blocks
> for ages.
>
> It hasn't been a big problem until now because logical block size has
> been equal to the hardware sector size. That's no longer a valid
> assumption.
> "
>
> Are the ATA/SCSI/etc specs at odds with each other about this?
Hardware specs aren't of concern here. The logical block concept is
there simply to give 9 bit addressing advantage, nothing more, nothing
less. If hardware's sector size doesn't match it, the lld should be
mapping the sector addresses and sizes and cdrom and a few other
drives have been doing that for ages. There's nothing new about
devices with sectors larger than 512 bytes.
Thanks.
--
tejun
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Konrad Rzeszutek <konrad@virtualiron.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Kay Sievers <kay.sievers@vrfy.org>,
jeff@garzik.org, linux-scsi@vger.kernel.org,
Mauelshagen@redhat.com, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, jens.axboe@oracle.com,
martin.petersen@oracle.com
Subject: Re: [dm-devel] Re: [PATCH 1/3] block: add alt_size
Date: Tue, 12 May 2009 09:53:05 +0900 [thread overview]
Message-ID: <4A08C871.9000100@kernel.org> (raw)
In-Reply-To: <20090511134534.GA32678@mars.virtualiron.com>
Konrad Rzeszutek wrote:
> .. snip ..
>>> Also, values with magic block counts, while there is no way to get the
>>> blocksize with the same interface, are pretty weird. I think the
>>> current "size" attribute is just a bug.
>> Logical block size is fixed at 512 bytes. Offset and size are always
>> represented in multiples of 512 bytes and only get converted to
>> hardware block size in the lld.
>
> That interpretation is at odds with the work that Martin Peterson is
> doing with the 4K support. In the e-mail titled: "Re: [PATCH 4 of 8] sd:
> Physical block size and alignment support",
> Message-ID:<yq1ab67b51p.fsf@sermon.lab.mkp.net> he says:
>
> "
> Konrad> about what a 'logical block', and 'physical block' is
> Konrad> vs. 'hardware sector' ?
>
> Well, another item on my todo list is to kill the notion of hardware
> sector completely. The protocols have been referring to logical blocks
> for ages.
>
> It hasn't been a big problem until now because logical block size has
> been equal to the hardware sector size. That's no longer a valid
> assumption.
> "
>
> Are the ATA/SCSI/etc specs at odds with each other about this?
Hardware specs aren't of concern here. The logical block concept is
there simply to give 9 bit addressing advantage, nothing more, nothing
less. If hardware's sector size doesn't match it, the lld should be
mapping the sector addresses and sizes and cdrom and a few other
drives have been doing that for ages. There's nothing new about
devices with sectors larger than 512 bytes.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-05-12 0:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 0:13 [GIT PATCH] block,scsi,libata: implement alt_size, take#2 Tejun Heo
2009-05-09 0:13 ` Tejun Heo
2009-05-09 0:13 ` [PATCH 1/3] block: add alt_size Tejun Heo
2009-05-09 0:13 ` Tejun Heo
2009-05-09 13:45 ` Kay Sievers
2009-05-09 13:45 ` Kay Sievers
2009-05-09 14:04 ` Tejun Heo
2009-05-09 14:04 ` Tejun Heo
2009-05-09 16:26 ` Kay Sievers
2009-05-11 13:45 ` [dm-devel] " Konrad Rzeszutek
2009-05-12 0:53 ` Tejun Heo [this message]
2009-05-12 0:53 ` Tejun Heo
2009-05-09 0:13 ` [PATCH 2/3] scsi: add scsi_device->alt_capacity Tejun Heo
2009-05-09 0:13 ` Tejun Heo
2009-05-09 4:23 ` James Bottomley
2009-05-09 16:09 ` Tejun Heo
2009-05-09 16:09 ` Tejun Heo
2009-05-09 16:23 ` James Bottomley
2009-05-10 1:26 ` Tejun Heo
2009-05-15 19:44 ` ATA ULD (was Re: [PATCH 2/3] scsi: add scsi_device->alt_capacity) Jeff Garzik
2009-05-09 0:13 ` [PATCH 3/3] libata: export HPA size as alt_size Tejun Heo
2009-05-09 0:13 ` Tejun Heo
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=4A08C871.9000100@kernel.org \
--to=tj@kernel.org \
--cc=Mauelshagen@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=konrad@virtualiron.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.