From: Rik van Riel <riel@redhat.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: linux-kernel@vger.kernel.org, npiggin@suse.de, akpm@osdl.org,
jeremy@goop.org, xen-devel@lists.xensource.com,
tmem-devel@oss.oracle.com, alan@lxorguk.ukuu.org.uk,
linux-mm@kvack.org, kurt.hackel@oracle.com,
Rusty Russell <rusty@rustcorp.com.au>,
dave.mccracken@oracle.com, Marcelo Tosatti <mtosatti@redhat.com>,
sunil.mushran@oracle.com, Avi Kivity <avi@redhat.com>,
Schwidefsky <schwidefsky@de.ibm.com>,
chris.mason@oracle.com, Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [RFC PATCH 1/4] (Take 2): tmem: Core API between kernel and tmem
Date: Tue, 07 Jul 2009 13:47:32 -0400 [thread overview]
Message-ID: <4A538A34.7060101@redhat.com> (raw)
In-Reply-To: <e5a93cf7-c24c-4bfe-bc4c-c24eb8e0290d@default>
Dan Magenheimer wrote:
> Tmem [PATCH 1/4] (Take 2): Core API between kernel and tmem
I like the cleanup of your patch series.
However, what remains is a fair bit of code.
It would be good to have performance numbers before
deciding whether or not to merge all this code.
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: linux-kernel@vger.kernel.org, npiggin@suse.de, akpm@osdl.org,
jeremy@goop.org, xen-devel@lists.xensource.com,
tmem-devel@oss.oracle.com, alan@lxorguk.ukuu.org.uk,
linux-mm@kvack.org, kurt.hackel@oracle.com,
Rusty Russell <rusty@rustcorp.com.au>,
dave.mccracken@oracle.com, Marcelo Tosatti <mtosatti@redhat.com>,
sunil.mushran@oracle.com, Avi Kivity <avi@redhat.com>,
Schwidefsky <schwidefsky@de.ibm.com>,
chris.mason@oracle.com, Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [RFC PATCH 1/4] (Take 2): tmem: Core API between kernel and tmem
Date: Tue, 07 Jul 2009 13:47:32 -0400 [thread overview]
Message-ID: <4A538A34.7060101@redhat.com> (raw)
In-Reply-To: <e5a93cf7-c24c-4bfe-bc4c-c24eb8e0290d@default>
Dan Magenheimer wrote:
> Tmem [PATCH 1/4] (Take 2): Core API between kernel and tmem
I like the cleanup of your patch series.
However, what remains is a fair bit of code.
It would be good to have performance numbers before
deciding whether or not to merge all this code.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: npiggin@suse.de, akpm@osdl.org, jeremy@goop.org,
xen-devel@lists.xensource.com, tmem-devel@oss.oracle.com,
kurt.hackel@oracle.com, Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, dave.mccracken@oracle.com,
linux-mm@kvack.org, chris.mason@oracle.com,
sunil.mushran@oracle.com, Avi Kivity <avi@redhat.com>,
Schwidefsky <schwidefsky@de.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
alan@lxorguk.ukuu.org.uk,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [RFC PATCH 1/4] (Take 2): tmem: Core API between kernel and tmem
Date: Tue, 07 Jul 2009 13:47:32 -0400 [thread overview]
Message-ID: <4A538A34.7060101@redhat.com> (raw)
In-Reply-To: <e5a93cf7-c24c-4bfe-bc4c-c24eb8e0290d@default>
Dan Magenheimer wrote:
> Tmem [PATCH 1/4] (Take 2): Core API between kernel and tmem
I like the cleanup of your patch series.
However, what remains is a fair bit of code.
It would be good to have performance numbers before
deciding whether or not to merge all this code.
next prev parent reply other threads:[~2009-07-07 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 16:18 [RFC PATCH 1/4] (Take 2): tmem: Core API between kernel and tmem Dan Magenheimer
2009-07-07 16:18 ` Dan Magenheimer
2009-07-07 17:47 ` Rik van Riel [this message]
2009-07-07 17:47 ` Rik van Riel
2009-07-07 17:47 ` Rik van Riel
2009-07-07 20:07 ` Dan Magenheimer
2009-07-07 20:07 ` Dan Magenheimer
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=4A538A34.7060101@redhat.com \
--to=riel@redhat.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=avi@redhat.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=chris.mason@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=dave.mccracken@oracle.com \
--cc=jeremy@goop.org \
--cc=kurt.hackel@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtosatti@redhat.com \
--cc=npiggin@suse.de \
--cc=rusty@rustcorp.com.au \
--cc=schwidefsky@de.ibm.com \
--cc=sunil.mushran@oracle.com \
--cc=tmem-devel@oss.oracle.com \
--cc=xen-devel@lists.xensource.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.