linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Brent Casavant <bcasavan@sgi.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>, Andi Kleen <ak@suse.de>,
	"Adam J. Richter" <adam@yggdrasil.com>,
	colpatch@us.ibm.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] Use MPOL_INTERLEAVE for tmpfs files
Date: Mon, 15 Nov 2004 16:07:29 -0600	[thread overview]
Message-ID: <Pine.SGI.4.58.0411151604580.20302@kzerza.americas.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0411111929370.2939-300000@localhost.localdomain>

On Thu, 11 Nov 2004, Hugh Dickins wrote:

> The first (against 2.6.10-rc1-mm5) being my reversion of NULL sbinfo
> in shmem.c, to make it easier for others to add things into sbinfo
> without having to worry about NULL cases.  So that goes back to
> allocating an sbinfo even for the internal mount: I've rounded up to
> L1_CACHE_BYTES to avoid false sharing, but even so, please test it out
> on your 512-way to make sure I haven't screwed up the scalability we
> got before - thanks.  If you find it okay, I'll send to akpm soonish.

OK, tried it at 508P (the last 4P had a hardware problem).  The
performance results are all in line with what we'd accomplished
with NULL sbinfo, so the patch is good by me.

Brent

-- 
Brent Casavant                          If you had nothing to fear,
bcasavan@sgi.com                        how then could you be brave?
Silicon Graphics, Inc.                    -- Queen Dama, Source Wars
--
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:"aart@kvack.org"> aart@kvack.org </a>

      parent reply	other threads:[~2004-11-15 22:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02  1:07 Brent Casavant
2004-11-02  1:43 ` Dave Hansen
2004-11-02  9:13 ` Andi Kleen
2004-11-02 15:46 ` Martin J. Bligh
2004-11-02 15:55   ` Andi Kleen
2004-11-02 16:55     ` Martin J. Bligh
2004-11-02 22:17       ` Brent Casavant
2004-11-02 22:51         ` Martin J. Bligh
2004-11-03  1:12           ` Brent Casavant
2004-11-03  1:30             ` Martin J. Bligh
2004-11-03  8:44           ` Hugh Dickins
2004-11-03  9:01             ` Andi Kleen
2004-11-03 16:32               ` Brent Casavant
2004-11-03 21:00                 ` Martin J. Bligh
2004-11-08 19:58                   ` Brent Casavant
2004-11-08 20:57                     ` Martin J. Bligh
2004-11-09 19:04                     ` Hugh Dickins
2004-11-09 20:09                       ` Martin J. Bligh
2004-11-09 21:08                         ` Hugh Dickins
2004-11-09 22:07                           ` Martin J. Bligh
2004-11-10  2:41                       ` Brent Casavant
2004-11-10 14:20                         ` Hugh Dickins
2004-11-11 19:48                       ` Hugh Dickins
2004-11-11 23:10                         ` Brent Casavant
2004-11-15 22:07                         ` Brent Casavant [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=Pine.SGI.4.58.0411151604580.20302@kzerza.americas.sgi.com \
    --to=bcasavan@sgi.com \
    --cc=adam@yggdrasil.com \
    --cc=ak@suse.de \
    --cc=colpatch@us.ibm.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@aracnet.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