linux-kernel - Re: [PATCH -mm] make swapin readahead skip over holes

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 11 Jan 2012 17:25:27 -0500
From:	KOSAKI Motohiro <kosaki.motohiro@...il.com>
To:	John Stoffel <john@...ffel.org>
Cc:	Christoph Lameter <cl@...ux.com>, Rik van Riel <riel@...hat.com>,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, Mel Gorman <mel@....ul.ie>,
	Johannes Weiner <hannes@...xchg.org>
Subject: Re: [PATCH -mm] make swapin readahead skip over holes

> Christoph> The assumptions by Kosaki are quite conservative.
>
> Just checking
>
> Christoph> What if one did not get a disk from the garbage heap but
> Christoph> instead has a state of the art storage cluster or simply an
> Christoph> SSD (in particular relevant now since HDs are in short
> Christoph> supply given the situation in Asia)?
>
> I don't know, I was just trying to make sure he thinks about disks
> which are slower than he expects, since there are lots of them still
> out there.

If you have a rotate disk, a bottoleneck is almost always IOPS, not
disk bandwidth.
at least when the systems are under swap-in, I can't imagine the system is under
disk bandwidth neck. Therefore we can eat free lunch if and only if we
don't increase
number of IOs.

In opposite, if you have much rich IO devices, that's more simple. You
don't need
worry about a few MB/s swap IO.
--
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/