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] [day] [month] [year] [list]
Date:	Mon, 06 Apr 2009 12:23:35 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Martin Schwidefsky <schwidefsky@...ibm.com>
CC:	Rik van Riel <riel@...hat.com>, akpm@...l.org,
	Nick Piggin <nickpiggin@...oo.com.au>, frankeh@...son.ibm.com,
	virtualization@...ts.osdl.org, linux-kernel@...r.kernel.org,
	virtualization@...ts.linux-foundation.org, linux-mm@...ck.org,
	hugh@...itas.com, Xen-devel <xen-devel@...ts.xensource.com>
Subject: Re: [patch 0/6] Guest page hinting version 7.

Martin Schwidefsky wrote:
> Why should the guest want to do preswapping? It is as expensive for
> the host to swap a page and get it back as it is for the guest (= one
> write + one read).

Yes, perhaps for swapping, but in general it makes sense for the guest 
to write the pages to backing store to prevent host swapping.  For swap 
pages there's no big benefit, but for file-backed pages its better for 
the guest to do it.

> The only thing you can gain by
> putting memory pressure on the guest is to free some of the memory that
> is used by the kernel for dentries, inodes, etc. 
>   

Well, that's also significant.  My point is that the guest has multiple 
ways in which it can relieve its own memory pressure in response to 
overall system memory pressure; its just that I happened to pick the 
example where its much of a muchness.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ