From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Arun <engineerarun@gmail.com>
Cc: Joshua Scoggins <theoretically.x64@gmail.com>,
Mike Snitzer <snitzer@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Detection of Advanced Format drives
Date: Tue, 27 Sep 2011 14:59:18 -0400 [thread overview]
Message-ID: <yq11uv1dd6h.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <CANLaLhbiLC-+azrdmf3_uPYS1zR3x-Yk9tA2b0U6_z72YSjQYQ@mail.gmail.com> (Arun's message of "Wed, 28 Sep 2011 00:06:16 +0530")
>>>>> "Arun" == Arun <engineerarun@gmail.com> writes:
Arun> Should I suppose that it is an already available piece of
Arun> information to the userland?
Yes, in the sysfs locations Mike mentioned:
/sys/block/foo/queue/physical_block_size
Or you can use the BLKPBSZGET ioctl.
Arun> Or do I need to modify the hdparm/fdisk code to get this piece of
Arun> info?
Recent hdparm versions will also report the right thing:
# hdparm -I /dev/sdc | grep Sector
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 512 bytes
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2011-09-27 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 9:55 Detection of Advanced Format drives Arun
2011-09-26 10:15 ` Alan Cox
2011-09-26 19:48 ` Joshua Scoggins
2011-09-26 20:09 ` Mike Snitzer
2011-09-27 17:59 ` Joshua Scoggins
2011-09-27 18:36 ` Arun
2011-09-27 18:59 ` Martin K. Petersen [this message]
2011-09-27 19:18 ` Arun
2011-09-27 20:10 ` Mark Knecht
2011-09-27 21:12 ` Arun
2011-09-27 21:44 ` Martin K. Petersen
2011-09-28 1:23 ` NamJae Jeon
[not found] ` <CANLaLhagmNFFrNxC88cyPqsx_j+-Y-WaAUCQpkR57z264Bn6Vw@mail.gmail.com>
2012-02-16 19:14 ` Martin K. Petersen
2011-09-26 21:01 ` Martin K. Petersen
2011-09-26 21:03 ` Martin K. Petersen
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=yq11uv1dd6h.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=engineerarun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@gmail.com \
--cc=theoretically.x64@gmail.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