Re: status of dm-crypt (alignment issues) on a SSD

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks a lot for your reply!

Luca Berra a dit:
> what you need on kernel side is having in sysfs
> under /sys/block/<device>
> queue/minimum_io_size
> queue/optimal_io_size
> queue/physical_block_size

These are present while running Debian's 2.6.32-5 linux kernel.

> on tool side,
> for util-linux
> ldd /sbin/fdisk | grep blkid

$ ldd /sbin/fdisk | grep blkid
        libblkid.so.1 => /lib/libblkid.so.1 (0x00007fd182e63000)

> strings /lib/libblkid.so.1 | grep queue/

$ strings /lib/libblkid.so.1 | grep queue/
	queue/minimum_io_size
	queue/optimal_io_size
	queue/physical_block_size

> for lvm
> strings /sbin/lvm |grep queue/

$ strings /sbin/lvm | grep queue/
	queue/optimal_io_size
	queue/minimum_io_size

> and so on.

So far, everything seems good as far as I understnad, but should
`cryptsetup` have 'queue' strings as well ? Mine (v1.1.3) doesn't. I
compiled 1.2.0-rc1 and it doesn't either. Is that a stopper of not?

Thanks,

-- 
mike dentifrice <fluor@xxxxxxxxxxx>

_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt


[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux