From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: tmem ephemeral page discarding Date: Mon, 3 Jun 2013 08:21:39 -0400 Message-ID: <20130603122139.GC6893@phenom.dumpdata.com> References: <6035A0D088A63A46850C3988ED045A4B5C1F482A@BITCOM1.int.sbss.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <6035A0D088A63A46850C3988ED045A4B5C1F482A@BITCOM1.int.sbss.com.au> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: James Harper Cc: dan.magenheimer@oracle.com, "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Sun, Jun 02, 2013 at 04:06:18AM +0000, James Harper wrote: > How does Xen manage ephemeral pages? Is there a way to manage the priority of pages in the ephemeral store? In my use case, I would prefer that an old page was automatically discarded to make room for a new page, and that pages that have been retrieved already are more likely to be discarded than a page that has not yet been retrieved. > In other words an LRU system with bounds. Right now the bounds are the amount of memory available and when Xen needs more memory the bounds gets decreased - which will discard the least used ephermeal pages. There is a tmem subop to actually set the cap (TMEMC_SET_CAP), which sets the cap value. However I am not seeing in the code anybody using it. Hmmm > Thanks > > James > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >