lkml.org 
[lkml]   [2009]   [May]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 3/6] ksm: change the KSM_REMOVE_MEMORY_REGION ioctl.
Hugh Dickins wrote:
>
> If KSM is to behave in the usual madvise way, it'll need to be informed
> of unmaps. And I suspect it may need to be informed of them, even if we
> let it continue to apply to empty address space. Because even with your
> more limited unsigned int nrpages interface, the caller can specify an
> enormous range on 64-bit, and ksm.c be fully occupied just incrementing
> from one absent page to the next.

That is a good point that i didnt think about it.
It is possible to make ksm "unmaped memory" aware by using find_vma(),
and skipped non mapped area.
But that start to look bad... (I can make that just by every place that
if_present_pte() fail, and then dont even hurt the scaning performence,
beacuse i will just check it when the first virtual address is not present)

But why not go go step by step?
We can first start with this ioctl interface, later when we add swapping
to the pages, we can have madvice, and still (probably easily) support
the ioctls by just calling from inside ksm the madvice functions for
that specific address)

I want to see ksm use madvice, but i believe it require some more
changes to mm/*.c, so it probably better to start with merging it when
it doesnt touch alot of stuff outisde ksm.c, and then to add swapping
and after that add madvice support (when the pages are swappable,
everyone can use it)

What you think about that?

> mmap's vma ranges confine the space
> to be searched, and instantiated pagetables confine it further: I think
> you're either going to need to rely upon those to confine your search
> area, or else enhance your own data structures to confine it.
>
> But I do appreciate the separation you've kept so far,
> and wouldn't want to tie it all together too closely.
>
> Hugh
>
> p.s. I wish you'd chosen different name than KSM - the kernel
> has supported shared memory for many years - and notice ksm.c itself
> says "Memory merging driver". "Merge" would indeed have been a less
> ambiguous term than "Share", but I think too late to change that now
> - except possibly in the MADV_ flag names?
>



\
 
 \ /
  Last update: 2009-05-06 17:33    [W:0.077 / U:6.036 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site