| 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
| ||
|
Date: Wed, 13 Sep 2006 09:06:42 -0400 From: Hubertus Franke <frankeh@...son.ibm.com> To: schwidefsky@...ibm.com CC: Rik van Riel <riel@...hat.com>, linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org, akpm@...l.org, nickpiggin@...oo.com.au, rhim@...gatech.edu Subject: Re: [patch 1/9] Guest page hinting: unused / free pages. Martin Schwidefsky wrote: > On Wed, 2006-09-13 at 08:06 -0400, Hubertus Franke wrote: > >>Martin Schwidefsky wrote: >> >>>On Tue, 2006-09-12 at 21:29 -0400, Rik van Riel wrote: >>> >>> >>>>Note that the transition _to_ volatile can also be batched >>>>and done somewhat lazily. For frequently mmaped pages that >>>>could end up saving us the transition the other way, too... >>> >>> >>>That would be helpful, only how to do it? We need some sort of list or >>>array where to store the pages that should be made volatile. The main >>>problem that I see is that you have to remove a page that is freed from >>>the list/array again, otherwise you would end up with a non page-cache >>>page being made volatile. That makes using per-cpu arrays hard since a >>>page can be freed on another cpu. >>> >> >> >>Martin. the point was that pages >>which are in the hold/cold lists are technically free. >>However we keep them stable. >>When the hot/cold list is spilled back to the buddy allocator >>we make them volatile in buld (i.e. through the array). > > > You mean unused. Yes ... > > >>So we only build the array for the duration of the bulk-release >>to the buddy allocator (and potentially the other way as well). >>Hence there is no "state" to maintain or track for the array. >>Pages in the hot/cold lists remain stable. >>This would not any of the problems you described as long as we hold >>the lock for the hot/cold list during buld-volatile. > > > I was not talking about free pages, and I don't think Rik was either. > The idea is to be lazy about the make-volatile calls. Put the pages for > which a make-volatile call should be done to some array/list and do a > bulk make-volatile. These pages are still in the page/swap cache. The > trouble is we have to be sure these pages have not been freed in the > meantime. Reread Rik's message. First message is about freeing pages. Second is about "to-volatile". I agree with you that if we batch "to-volatile" we need to keep state, which does seem to have the problem you describe. On the fly design thoughts .. Let's assume we want to keep in the order of 1K pages to batch. If we hash the pages that are made logically volatile but have not been submitted yet, then on free_page we check whether the page is hashed and if so remove it from the hashtable. If the hashtable fills up we commit. The hashtable is global or node specific (can't be per-cpu as you pointed out). This can be done reasonable efficient. But another trouble you have not mentioned is what happens to pages with pending make-volatile that need to and/or have been made stable in the meantime. They too need to be removed from this pending list. -- Hubertus > > The bulk set-unused/set-stable to the buddy allocator should not be to > problematic. We just have to find new places where to do the calls. > - 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