All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Dave Hansen <dave@sr71.net>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] [RESEND][v4] x86: rework tlb range flushing code
Date: Thu, 31 Jul 2014 09:58:45 -0700	[thread overview]
Message-ID: <53DA75C5.5010607@zytor.com> (raw)
In-Reply-To: <20140731154052.C7E7FBC1@viggo.jf.intel.com>

On 07/31/2014 08:40 AM, Dave Hansen wrote:
> x86 Maintainers,
> 
> I've sent this a couple of times and resolved all the feedback
> I've received.  It has sign-offs from Mel and Rik.  Could this
> get picked up in to the x86 tree, please?
> 
> Changes from v3:
>  * Include the patch I was using to gather detailed statistics
>    about the length of the ranged TLB flushes
>  * Fix some documentation typos
>  * Add a patch to rework the remote tlb flush code to plumb the
>    tracepoints in easier, and add missing tracepoints
>  * use __print_symbolic() for the human-readable tracepoint
>    descriptions
>  * change an int to bool in patch 1
>  * Specifically call out that we removed itlb vs. dtlb logic
> 
> Changes from v2:
>  * Added a brief comment above the ceiling tunable
>  * Updated the documentation to mention large pages and say
>    "individual flush" instead of invlpg in most cases.
> 
> I've run this through a variety of systems in the LKP harness,
> as well as running it on my desktop for a few days.  I'm yet to
> see an to see if any perfmance regressions (or gains) show up.
> 

Thanks for the resend.  Applied.

	-hpa


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

WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Dave Hansen <dave@sr71.net>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] [RESEND][v4] x86: rework tlb range flushing code
Date: Thu, 31 Jul 2014 09:58:45 -0700	[thread overview]
Message-ID: <53DA75C5.5010607@zytor.com> (raw)
In-Reply-To: <20140731154052.C7E7FBC1@viggo.jf.intel.com>

On 07/31/2014 08:40 AM, Dave Hansen wrote:
> x86 Maintainers,
> 
> I've sent this a couple of times and resolved all the feedback
> I've received.  It has sign-offs from Mel and Rik.  Could this
> get picked up in to the x86 tree, please?
> 
> Changes from v3:
>  * Include the patch I was using to gather detailed statistics
>    about the length of the ranged TLB flushes
>  * Fix some documentation typos
>  * Add a patch to rework the remote tlb flush code to plumb the
>    tracepoints in easier, and add missing tracepoints
>  * use __print_symbolic() for the human-readable tracepoint
>    descriptions
>  * change an int to bool in patch 1
>  * Specifically call out that we removed itlb vs. dtlb logic
> 
> Changes from v2:
>  * Added a brief comment above the ceiling tunable
>  * Updated the documentation to mention large pages and say
>    "individual flush" instead of invlpg in most cases.
> 
> I've run this through a variety of systems in the LKP harness,
> as well as running it on my desktop for a few days.  I'm yet to
> see an to see if any perfmance regressions (or gains) show up.
> 

Thanks for the resend.  Applied.

	-hpa



  parent reply	other threads:[~2014-07-31 16:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 15:40 [PATCH 0/7] [RESEND][v4] x86: rework tlb range flushing code Dave Hansen
2014-07-31 15:40 ` Dave Hansen
2014-07-31 15:40 ` [PATCH 1/7] x86: mm: clean up tlb " Dave Hansen
2014-07-31 15:40   ` Dave Hansen
2014-07-31 16:09   ` [tip:x86/mm] x86/mm: Clean up the TLB " tip-bot for Dave Hansen
2014-07-31 15:40 ` [PATCH 2/7] x86: mm: rip out complicated, out-of-date, buggy TLB flushing Dave Hansen
2014-07-31 15:40   ` Dave Hansen
2014-07-31 16:09   ` [tip:x86/mm] x86/mm: Rip " tip-bot for Dave Hansen
2014-07-31 15:40 ` [PATCH 3/7] x86: mm: fix missed global TLB flush stat Dave Hansen
2014-07-31 15:40   ` Dave Hansen
2014-07-31 16:10   ` [tip:x86/mm] x86/mm: Fix " tip-bot for Dave Hansen
2014-07-31 15:40 ` [PATCH 4/7] x86: mm: unify remote invlpg code Dave Hansen
2014-07-31 15:40   ` Dave Hansen
2014-07-31 16:10   ` [tip:x86/mm] x86/mm: Unify remote INVLPG code tip-bot for Dave Hansen
2014-07-31 15:40 ` [PATCH 5/7] x86: mm: add tracepoints for TLB flushes Dave Hansen
2014-07-31 15:40   ` Dave Hansen
2014-07-31 16:10   ` [tip:x86/mm] x86/mm: Add " tip-bot for Dave Hansen
2014-07-31 15:41 ` [PATCH 6/7] x86: mm: new tunable for single vs full TLB flush Dave Hansen
2014-07-31 15:41   ` Dave Hansen
2014-07-31 16:10   ` [tip:x86/mm] x86/mm: New " tip-bot for Dave Hansen
2014-07-31 15:41 ` [PATCH 7/7] x86: mm: set TLB flush tunable to sane value (33) Dave Hansen
2014-07-31 15:41   ` Dave Hansen
2014-07-31 16:11   ` [tip:x86/mm] x86/mm: Set " tip-bot for Dave Hansen
2014-07-31 16:58 ` H. Peter Anvin [this message]
2014-07-31 16:58   ` [PATCH 0/7] [RESEND][v4] x86: rework tlb range flushing code H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2014-07-01 16:48 Dave Hansen
2014-07-01 16:48 ` Dave Hansen
2014-07-02 19:04 ` Davidlohr Bueso
2014-07-02 19:04   ` Davidlohr Bueso

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=53DA75C5.5010607@zytor.com \
    --to=hpa@zytor.com \
    --cc=dave@sr71.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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.