| 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
| ||
|
Date: Thu, 21 Apr 2011 14:29:37 -0400 From: Chris Mason <chris.mason@...cle.com> To: Christoph Hellwig <hch@...radead.org> Cc: Andreas Dilger <adilger@...ger.ca>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-ext4 <linux-ext4@...r.kernel.org>, xfs <xfs@....sgi.com>, jack <jack@...e.cz>, axboe <axboe@...nel.dk>, dchinner <dchinner@...hat.com> Subject: Re: buffered writeback torture program Excerpts from Christoph Hellwig's message of 2011-04-21 14:08:05 -0400: > On Thu, Apr 21, 2011 at 02:02:43PM -0400, Chris Mason wrote: > > For this program, they are almost all dirty pages. > > > > I tried patching it to give up if we seek but it is still pretty slow. > > There's something else going on in addition to the xfs clustering being > > too aggressive. > > I'm not sure where you this beeing to agressive from - it's doing > exactly the same amount of I/O as a filesystem writing out a single > page from ->writepage or using write_cache_pages (either directly > or as a copy) as ->writepages. The only thing special compared to > the no ->writepages case is that it's submitting a large I/O > from the first ->writepage call. > Ok, I see what you mean. The clustering code stops once it hits nr_to_write, I missed that. So we shouldn't be doing more than a single writepages call. -chris -- 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
Powered by blists - more mailing lists