From: Rik van Riel <riel@redhat.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
npiggin@suse.de, chris.mason@oracle.com, kurt.hackel@oracle.com,
dave.mccracken@oracle.com, Avi Kivity <avi@redhat.com>,
jeremy@goop.org, alan@lxorguk.ukuu.org.uk,
Rusty Russell <rusty@rustcorp.com.au>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
akpm@osdl.org, Marcelo Tosatti <mtosatti@redhat.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
tmem-devel@oss.oracle.com, sunil.mushran@oracle.com,
linux-mm@kvack.org
Subject: Re: [RFC PATCH 2/4] tmem: precache implementation (layered on tmem)
Date: Fri, 19 Jun 2009 22:28:22 -0400 [thread overview]
Message-ID: <4A3C4946.6030100@redhat.com> (raw)
In-Reply-To: <67c05b05-c8e2-4e8f-a234-52a86e657404@default>
Dan Magenheimer wrote:
> @@ -110,6 +111,9 @@
> s->s_qcop = sb_quotactl_ops;
> s->s_op = &default_op;
> s->s_time_gran = 1000000000;
> +#ifdef CONFIG_PRECACHE
> + s->precache_poolid = -1;
> +#endif
> }
> out:
> return s;
Please generate your patches with -up so we can see
which functions are being modified by each patch hunk.
That makes it a lot easier to find the context and
see what you are trying to do.
--
All rights reversed.
--
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-20 2:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 23:53 [RFC] transcendent memory for Linux Dan Magenheimer
2009-06-20 1:35 ` [RFC PATCH 0/4] transcendent memory ("tmem") " Dan Magenheimer
2009-06-20 1:35 ` [RFC PATCH 1/4] tmem: infrastructure for tmem layer Dan Magenheimer
2009-06-20 1:50 ` Rik van Riel
2009-06-20 1:35 ` [RFC PATCH 2/4] tmem: precache implementation (layered on tmem) Dan Magenheimer
2009-06-20 2:28 ` Rik van Riel [this message]
2009-06-20 1:36 ` [RFC PATCH 3/4] tmem: preswap " Dan Magenheimer
2009-06-20 1:36 ` [RFC PATCH 4/4] tmem: interface code for tmem on top of xen Dan Magenheimer
2009-06-22 11:27 ` [RFC] transcendent memory for Linux Martin Schwidefsky
2009-06-22 20:41 ` Dan Magenheimer
2009-06-22 14:31 ` Chris Friesen
2009-06-22 20:50 ` Dan Magenheimer
2009-06-24 15:04 ` Pavel Machek
2009-06-29 14:34 ` Dan Magenheimer
2009-06-29 20:36 ` Pavel Machek
2009-06-29 21:13 ` Dan Magenheimer
2009-06-29 21:23 ` Jeremy Fitzhardinge
2009-06-29 21:57 ` Dan Magenheimer
2009-06-29 22:15 ` Jeremy Fitzhardinge
2009-06-30 21:21 ` Dan Magenheimer
2009-06-30 22:46 ` Jeremy Fitzhardinge
2009-07-01 23:02 ` Dan Magenheimer
2009-07-01 23:31 ` Jeremy Fitzhardinge
2009-07-02 6:38 ` Pavel Machek
2009-07-02 14:03 ` Dan Magenheimer
2009-06-27 13:18 ` Linus Walleij
2009-06-28 7:42 ` Avi Kivity
2009-06-29 14:44 ` Dan Magenheimer
2009-07-01 3:41 ` Roland Dreier
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=4A3C4946.6030100@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 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).