linux-kernel - RE: [RFC/PATCH] - revert generic_fillattr stat->blksize to PAGE_CACHE

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]

Message-ID: <015301c70201$94e88e00$0200a8c0@nuitysystems.com>
Date:	Mon, 6 Nov 2006 16:13:39 -0800
From:	"Hua Zhong" <hzhong@...il.com>
To:	"'Andreas Dilger'" <adilger@...sterfs.com>,
	"'Eric Sandeen'" <sandeen@...hat.com>
Cc:	"'Christoph Hellwig'" <hch@...radead.org>,
	"'Linux Kernel Mailing List'" <linux-kernel@...r.kernel.org>,
	"'linux-fsdevel'" <linux-fsdevel@...r.kernel.org>,
	"'Theodore Tso'" <tytso@....edu>
Subject: RE: [RFC/PATCH] - revert generic_fillattr stat->blksize to PAGE_CACHE_SIZE

> Actually, rather than blindly revert to pre-patch behaviour 
> it would be worthwhile to determine if PAGE_SIZE isn't the 
> better value.  In some cases people don't understand that 
> i_blksize is the "optimal IO size"
> and instead assume it is the filesystem blocksize.  I saw a 
> few that were e.g. 512 and that can't be very useful.

Of course the name i_blksize is very clear on that. :-)
 
> Cheers, Andreas
> --
> Andreas Dilger
> Principal Software Engineer
> Cluster File Systems, Inc.
> 
> -
> 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/

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