| 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
| ||
|
Message-ID: <20100913192626.GA15092@sig21.net> Date: Mon, 13 Sep 2010 21:26:26 +0200 From: Johannes Stezenbach <js@...21.net> To: dave b <db.pub.mail@...il.com> Cc: Florian Mickler <florian@...kler.org>, linux-kernel@...r.kernel.org, linux-mm@...ck.org, linux-fsdevel@...r.kernel.org Subject: Re: block cache replacement strategy? On Tue, Sep 14, 2010 at 05:09:31AM +1000, dave b wrote: > On 14 September 2010 01:21, Johannes Stezenbach <js@...21.net> wrote: > > On Fri, Sep 10, 2010 at 06:02:48PM +0200, Johannes Stezenbach wrote: > >> > >> Linear read heuristic might be a good guess, but it would > >> be nice to hear a comment from a vm/fs expert which > >> confirms this works as intended. > > > > Anyway I found lmdd (from lmbench) can do random reads, > > and indeed causes the data to enter the block (page?) cache, > > replacing the previous data. > > I am no expert, but what did you think would happen if you did dd > twice from /dev/zero? > but... Honestly what do you think will be cached? It's not from /dev/zero, it is from file to /dev/null. It all started with me wanting to compare disk read bandwidth vs. read bandwidth of my root partition via dm-crypt + LVM, and then wondering why dd from raw disk seemed to be cached while dd from crypted root partition didn't. Johannes -- 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