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, 23 Jul 2014 14:17:21 +0100
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	Linda Walsh <lkml@...nx.org>
Cc:	Dave Chinner <david@...morbit.com>,
	Linux-Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Howto tell kernel to use 4096 as granularity & minimum size?

On Mon, 21 Jul 2014 13:45:22 -0700
Linda Walsh <lkml@...nx.org> wrote:

> Dave Chinner wrote:
> >
> >> I can partition the disk and setup the allocation size
> >> to 4096, but I'd like to tell the kernel to use a
> >> virtual-size of 4096 for the sector as an additional
> >> performance 'hint', so nothing will even try to use
> >> smaller i/o's than that.
> >>     
> >
> > Just format the filesystem with 4k sector size.
> ---
>     Good idea,  though.. I wanted to set it for the whole "disk"(array)
> as it (multiple 4T drives) will be subdivided into multiple filesystems
> and have lvm and a partition table under the file system(s),
> so telling the kernel to only do 4K alloc+io's to the whole thing
> would cover the most with the least.

Also before you format it read the specification if you are using SATA
drives. The disk is not necessarily aligned so that the physical/logical
block boundary is as you'd expect. Some devices have a partial physical
sector at the start in order to make it happen to work nicely with legacy
software.

Good fdisk tools know about this. It's in the ATA8 specification for
identify.

Alan
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ