From: Izik Eidus <ieidus@redhat.com>
To: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: aarcange@redhat.com, akpm@linux-foundation.org,
nickpiggin@yahoo.com.au, chrisw@redhat.com, riel@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH mmotm] ksm: stop scan skipping pages
Date: Mon, 08 Jun 2009 23:12:47 +0300 [thread overview]
Message-ID: <4A2D70BF.9090605@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0906081852540.8764@sister.anvils>
Hugh Dickins wrote:
> On Mon, 8 Jun 2009, Izik Eidus wrote:
>
>> Thanks for the fix,
>> (I saw it while i wrote the RFC patch for the madvise, but beacuse that i
>> thought that the RFC fix this (you can see the removel of the second call to
>> scan_get_next_index()), and we move to madvise, I thought that no patch is
>> needed for this code, guess I was wrong)
>>
>
> Ah, no, I hadn't noticed that, this patch is from several weeks ago,
> before you even posted the madvise() version.
>
> I think myself that we ought to fix the algorithm as it stands now in
> mmotm, rather than hiding the fix in amongst later interface changes.
>
> But it's not a big deal, so long as it gets fixed in the end.
>
> By the time Andrew sends KVM to Linus, it shouldn't be the
> patches currently in mmotm with more on top:
So you want a repost of all the patchs?, in that case any value to keep
this stuff in Andrew tree right now?
Wouldnt it speed our development if we will keep it outside, and then
repost the whole thing?
> they should be
> re-presented with all trace of /dev/ksm gone by then.
>
> Hugh
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-06-08 20:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 0:30 [PATCH 0/4] RFC - ksm api change into madvise Izik Eidus
2009-05-14 0:30 ` [PATCH 1/4] madvice: add MADV_SHAREABLE and MADV_UNSHAREABLE calls Izik Eidus
2009-05-14 0:30 ` [PATCH 2/4] mmlist: share mmlist with ksm Izik Eidus
2009-05-14 0:30 ` [PATCH 3/4] ksm: change ksm api to use madvise instead of ioctls Izik Eidus
2009-05-14 0:30 ` [PATCH 4/4] ksm: add support for scanning procsses that were not modifided to use ksm Izik Eidus
2009-06-08 16:18 ` [PATCH 0/4] RFC - ksm api change into madvise Hugh Dickins
2009-06-08 16:35 ` [PATCH mmotm] ksm: stop scan skipping pages Hugh Dickins
2009-06-08 17:42 ` Izik Eidus
2009-06-08 18:01 ` Hugh Dickins
2009-06-08 20:12 ` Izik Eidus [this message]
2009-06-08 21:05 ` Hugh Dickins
2009-06-08 17:17 ` [PATCH 0/4] RFC - ksm api change into madvise Izik Eidus
2009-06-08 18:32 ` Hugh Dickins
2009-06-08 20:10 ` Izik Eidus
2009-06-09 4:48 ` Izik Eidus
2009-06-09 17:24 ` Hugh Dickins
2009-06-09 19:27 ` Hugh Dickins
2009-06-10 6:28 ` Izik Eidus
2009-06-11 16:57 ` Hugh Dickins
2009-06-12 21:49 ` Izik Eidus
2009-06-08 22:57 ` Andrea Arcangeli
2009-06-13 15:04 ` Hugh Dickins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A2D70BF.9090605@redhat.com \
--to=ieidus@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=chrisw@redhat.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=riel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).