From: Xiaotian Feng <dfeng@redhat.com>
Cc: Xiaotian Feng <dfeng@redhat.com>,
linux-mm@kvack.org, linux-nfs@vger.kernel.org,
netdev@vger.kernel.org, cl@linux-foundation.org,
a.p.zijlstra@chello.nl, lwang@redhat.com, penberg@cs.helsinki.fi,
davem@davemloft.net
Subject: Re: [PATCH RHEL6 RESEND] kernel performance optimization with CONFIG_DEBUG_RODATA
Date: Wed, 28 Jul 2010 19:03:04 +0800 [thread overview]
Message-ID: <4C500E68.5040309@redhat.com> (raw)
In-Reply-To: <20100728110043.27677.13908.sendpatchset@dhcp-65-180.nay.redhat.com>
oops, script got some wrong, sorry for the noise... please ignore the
mail ...
--
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>
prev parent reply other threads:[~2010-07-28 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 11:00 [PATCH RHEL6 RESEND] kernel performance optimization with CONFIG_DEBUG_RODATA Xiaotian Feng
2010-07-28 11:03 ` Xiaotian Feng [this message]
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=4C500E68.5040309@redhat.com \
--to=dfeng@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=cl@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lwang@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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).