linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	linux-mm@kvack.org, kamezawa.hiroyu@jp.fujitsu.com,
	akpm@linux-foundation.org
Subject: Re: [PATCH] hugeltb: Mark hugelb_max_hstate __read_mostly
Date: Fri, 15 Jun 2012 09:50:00 -0500 (CDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1206150948120.20541@router.home> (raw)
In-Reply-To: <20120615143342.GE8100@tiehlicka.suse.cz>

On Fri, 15 Jun 2012, Michal Hocko wrote:

> > Thats all? There is no performance gain from this change?
>
> Is that required in order to put data in the read mostly section?

I thought so. The read_mostly section is specially designed for data that
causes excessive cacheline bounces and has to be grouped with rarely
accessed other data. That was at least the intend when we created it.



--
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>

  reply	other threads:[~2012-06-15 14:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 13:56 Aneesh Kumar K.V
2012-06-14 14:12 ` Michal Hocko
2012-06-14 20:43   ` Christoph Lameter
2012-06-15  6:08     ` Aneesh Kumar K.V
2012-06-15 13:57       ` Christoph Lameter
2012-06-15 14:33         ` Michal Hocko
2012-06-15 14:50           ` Christoph Lameter [this message]
2012-06-22 22:06             ` Andrew Morton
2012-06-15  6:10   ` Aneesh Kumar K.V
2012-06-22 22:03     ` Andrew Morton

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=alpine.DEB.2.00.1206150948120.20541@router.home \
    --to=cl@linux.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    /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