All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Dave Hansen <dave@sr71.net>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: vmstats: tlb flush counters
Date: Wed, 17 Jul 2013 07:36:32 +0800	[thread overview]
Message-ID: <20130716233632.GD30164@hacker.(null)> (raw)
In-Reply-To: <20130716155304.AF1A88F8@viggo.jf.intel.com>

On Tue, Jul 16, 2013 at 08:53:04AM -0700, Dave Hansen wrote:
>I was investigating some TLB flush scaling issues and realized
>that we do not have any good methods for figuring out how many
>TLB flushes we are doing.
>
>It would be nice to be able to do these in generic code, but the
>arch-independent calls don't explicitly specify whether we
>actually need to do remote flushes or not.  In the end, we really
>need to know if we actually _did_ global vs. local invalidations,
>so that leaves us with few options other than to muck with the
>counters from arch-specific code.
>
>Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
>

There is no context in the patch?

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

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

  parent reply	other threads:[~2013-07-16 23:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16 15:53 [PATCH] mm: vmstats: tlb flush counters Dave Hansen
2013-07-16 15:53 ` Dave Hansen
2013-07-16 23:36 ` Wanpeng Li
2013-07-16 23:36 ` Wanpeng Li [this message]
2013-07-16 23:43   ` Dave Hansen

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='20130716233632.GD30164@hacker.(null)' \
    --to=liwanp@linux.vnet.ibm.com \
    --cc=dave@sr71.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.