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: <20070728013251.7c110223.grundig@teleline.es>
Date:	Sat, 28 Jul 2007 01:34:24 +0200 (added by postmaster@...ra.es)
From:	grundig <grundig@...eline.es>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Indan Zupancic <indan@....nu>, 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)

El Fri, 27 Jul 2007 15:06:14 -0700, Arjan van de Ven <arjan@...radead.org> escribió:

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

If there hasn't be much IO for some time, it looks quite reasonable to expect
that there won't be more in the near future. As most of heuristics can fail, but
then this is a feature mostly for desktops, not servers.

There's an old saying that says something like "an open source project starts
dying when new people can't participate in the project no matter how hard
they try". It's hard to understand why there's so many people opposing to
this when other more controversial features are merged much faster, (like, fe. 
the UIO driver framework). 
-
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/