linux-kernel - Re: swap-prefetch: A smart way to make good use of idle resources (was: updatedb)

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: <33456.81.207.0.53.1185574821.squirrel@secure.samage.net>
Date:	Sat, 28 Jul 2007 00:20:21 +0200 (CEST)
From:	"Indan Zupancic" <indan@....nu>
To:	"Arjan van de Ven" <arjan@...radead.org>
Cc:	"Al Boldi" <a1426z@...ab.com>, linux-kernel@...r.kernel.org
Subject: Re: swap-prefetch:  A smart way to make good use of idle resources 
      (was: updatedb)

On Sat, July 28, 2007 00:06, Arjan van de Ven wrote:
> On Fri, 2007-07-27 at 23:51 +0200, Indan Zupanci
>> > also, they take up seek time (5 to 10 msec), so if you were to read
>> > something else at the time you get additional latency.
>>
>> If there's other disk activity swap prefetch shouldn't do much, so this isn't
>> really true.
>
> how do you know there will be other activity? You start the IO and that
> basically blacks out the disk for 5 to 10 ms. If the "real" IO gets
> submitted in that time you add latency. You cannot predict that IO
> happening or not happening.

Ah, in that way. Yes, you right about that (though NCQ might help then?),
but that's true for all disk activity. Though I think swap prefetch didn't want
to run when there was CPU activity, so that would reduce the chance that
new IO is submitted right at that moment. I think in practice this isn't worth
worrying about, the real issue is the extra disk activity in the first place.

Greetings,

Indan


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