linux-ext4 - Re: [RFC] Defragmentation interface

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 3 Nov 2006 20:38:00 +0100
From:	Jan Kara <jack@....cz>
To:	Andreas Dilger <adilger@...sterfs.com>
Cc:	David Chinner <dgc@....com>, linux-fsdevel@...r.kernel.org,
	linux-ext4@...r.kernel.org
Subject: Re: [RFC] Defragmentation interface

> On Nov 03, 2006  15:30 +0100, Jan Kara wrote:
> > > - stripe unit and stripe width need to be exposed so defrag too
> > >   can make correct placement decisions.
> >   fs-specific thing...
> 
> I think this is not just XFS-specific.  It is very desirable to align
> large IO to the RAID stripe so that if you write stripe_width bytes
> you don't do 2 expensive read-modify-write steps, but rather a single
> write operation.  Also RAID controllers have (large) internal cache
> "lines" and having aligned reads can help noticably, and also if array
> is doing RAID parity checking to avoid overhead of doing this for two
> stripes instead of one.
  I see, thanks for information. On the other hand this is rather an
underlying block device feature than a fs thing, isn't it? So does it
make sence to pass this information via fs interface?

								Honza
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html