mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Alok kataria <alokkataria1@gmail.com>, Andi Kleen <ak@suse.de>,
	Ben Herrenschmidt <benh@kernel.crashing.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: ARCH_FREE_PTE_NR 5350 on x86_64
Date: Mon, 22 Oct 2007 19:22:44 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710221913250.18548@blonde.wat.veritas.com> (raw)
In-Reply-To: <200710152236.24789.nickpiggin@yahoo.com.au>

On Mon, 15 Oct 2007, Nick Piggin wrote:
> On Monday 15 October 2007 16:54, Alok kataria wrote:
> >
> > Looking at the tlb_flush code path and its co-relation with
> > ARCH_FREE_PTE_NR, on x86-64 architecture. I think we still don't use
> > the ARCH_FREE_PTE_NR of 5350 as the caching value for the mmu_gathers
> > structure, instead fallback to using 506 due to some typo errors in
> > the code.
> >
> > Found this link in the archives.
> >
> > http://www.ussg.iu.edu/hypermail/linux/kernel/0509.1/1821.html
> >
> > I don't think anything has been done on this yet (looked at 2.6.23).
> > Do let me know if its only a typo that needs a fix, or we are still
> > waiting for some other other changes to come into effect.
> 
> ARCH_FREE_PTE_NR should probably just get ripped out completely at
> this point. Something similar (but working) could be added back if
> anybody actually had a workload where it helps to increase the mmu
> batch size.

Agreed.  No hurry, but thanks to Alok for reminding us.
CC'ing Ben since he's the one most active in mmu_gathering these days.
CC'ing Thomas lest he's puzzling over it in the x86 merge.

Hugh

  reply	other threads:[~2007-10-22 18:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15  6:54 Alok kataria
2007-10-15 12:36 ` Nick Piggin
2007-10-22 18:22   ` Hugh Dickins [this message]
2007-10-22 20:29     ` Benjamin Herrenschmidt

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.LNX.4.64.0710221913250.18548@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=ak@suse.de \
    --cc=alokkataria1@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®