From: Andrea Arcangeli <aarcange@redhat.com>
To: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: Izik Eidus <ieidus@redhat.com>, Rik van Riel <riel@redhat.com>,
Chris Wright <chrisw@redhat.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: KSM: current madvise rollup
Date: Wed, 1 Jul 2009 12:33:14 +0200 [thread overview]
Message-ID: <20090701103314.GB14272@random.random> (raw)
In-Reply-To: <Pine.LNX.4.64.0907010057320.4255@sister.anvils>
Hi Hugh!
On Wed, Jul 01, 2009 at 03:03:58AM +0100, Hugh Dickins wrote:
> up with evidence for doing it differently - I think there's scope
> for academic papers on the behaviour of the unstable tree.
Eheh, I covered some of the behaviour of the unstable tree in the KSM
paper @ LinuxSymposium (downloadable in a few weeks) and I will ""try""
to cover some of it in my presentation as well ;).
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Arcangeli <aarcange@redhat.com>
To: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: Izik Eidus <ieidus@redhat.com>, Rik van Riel <riel@redhat.com>,
Chris Wright <chrisw@redhat.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: KSM: current madvise rollup
Date: Wed, 1 Jul 2009 12:33:14 +0200 [thread overview]
Message-ID: <20090701103314.GB14272@random.random> (raw)
In-Reply-To: <Pine.LNX.4.64.0907010057320.4255@sister.anvils>
Hi Hugh!
On Wed, Jul 01, 2009 at 03:03:58AM +0100, Hugh Dickins wrote:
> up with evidence for doing it differently - I think there's scope
> for academic papers on the behaviour of the unstable tree.
Eheh, I covered some of the behaviour of the unstable tree in the KSM
paper @ LinuxSymposium (downloadable in a few weeks) and I will ""try""
to cover some of it in my presentation as well ;).
--
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-07-01 10:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 14:14 KSM: current madvise rollup Hugh Dickins
2009-06-29 14:14 ` Hugh Dickins
2009-06-30 9:52 ` Izik Eidus
2009-06-30 9:52 ` Izik Eidus
2009-06-30 15:57 ` Hugh Dickins
2009-06-30 15:57 ` Hugh Dickins
2009-06-30 18:41 ` Izik Eidus
2009-06-30 18:41 ` Izik Eidus
2009-07-01 2:03 ` Hugh Dickins
2009-07-01 2:03 ` Hugh Dickins
2009-07-01 9:50 ` Izik Eidus
2009-07-01 9:50 ` Izik Eidus
2009-07-08 21:07 ` Hugh Dickins
2009-07-08 21:07 ` Hugh Dickins
2009-07-09 15:37 ` Izik Eidus
2009-07-09 15:37 ` Izik Eidus
2009-07-10 13:43 ` Hugh Dickins
2009-07-10 13:43 ` Hugh Dickins
2009-07-10 22:42 ` Izik Eidus
2009-07-10 22:42 ` Izik Eidus
2009-07-10 22:49 ` Izik Eidus
2009-07-10 22:49 ` Izik Eidus
2009-07-11 19:22 ` Hugh Dickins
2009-07-11 19:22 ` Hugh Dickins
2009-07-11 21:22 ` Izik Eidus
2009-07-11 21:22 ` Izik Eidus
2009-07-12 14:44 ` Hugh Dickins
2009-07-12 14:44 ` Hugh Dickins
2009-07-13 18:28 ` Izik Eidus
2009-07-13 18:28 ` Izik Eidus
2009-07-01 10:33 ` Andrea Arcangeli [this message]
2009-07-01 10:33 ` Andrea Arcangeli
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=20090701103314.GB14272@random.random \
--to=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=chrisw@redhat.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=ieidus@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.