linux-kernel - Re: Detection of Advanced Format drives

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 28 Sep 2011 10:23:56 +0900
From:	NamJae Jeon <linkinjeon@...il.com>
To:	"Martin K. Petersen" <martin.petersen@...cle.com>
Cc:	Arun <engineerarun@...il.com>, Mark Knecht <markknecht@...il.com>,
	Joshua Scoggins <theoretically.x64@...il.com>,
	Mike Snitzer <snitzer@...il.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	linux-kernel@...r.kernel.org
Subject: Re: Detection of Advanced Format drives

2011/9/28 Martin K. Petersen <martin.petersen@...cle.com>:
>>>>>> "Arun" == Arun  <engineerarun@...il.com> writes:
>
> Arun> A quick check of hdparm tells me that it is using the SG_IO ioctl
> Arun> for the ATA_OP_PIDENTIFY command. Maybe I have some hopes of
> Arun> having a correct result with the BLKPBSZGET ioctl. Will check that
> Arun> out.
>
> hdparm and the kernel are looking the same place for the physical block
> size. There should be no discrepancy between what hdparm can see and
> what's reported in physical_block_size by the kernel. The BLKPBSZGET
> returns the same topology parameter as sysfs' physical_block_size.
>
> --
> Martin K. Petersen      Oracle Linux Engineering
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
plz remember, There are native 4k and 512B emulate.
In case of 512B emulate, you can see logical block size is 512Byte and
physical block size is 4KB.
Although you can access 512Byte, It should be access per 4KB in order
to prevent the loss of performance by RMW penalty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/