From: Dave Hansen <dave.hansen@intel.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
David Rientjes <rientjes@google.com>,
linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: Flush the TLB for a single address in a huge page
Date: Thu, 23 Jul 2015 09:55:33 -0700 [thread overview]
Message-ID: <55B11C85.5070900@intel.com> (raw)
In-Reply-To: <20150723161644.GG27052@e104818-lin.cambridge.arm.com>
On 07/23/2015 09:16 AM, Catalin Marinas wrote:
> Anyway, if you want to keep the option of a full TLB flush for x86 on
> huge pages, I'm happy to repost a v2 with a separate
> flush_tlb_pmd_huge_page that arch code can define as it sees fit.
I think your patch is fine on x86. We need to keep an eye out for any
regressions, but I think it's OK.
--
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: Dave Hansen <dave.hansen@intel.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
David Rientjes <rientjes@google.com>,
linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: Flush the TLB for a single address in a huge page
Date: Thu, 23 Jul 2015 09:55:33 -0700 [thread overview]
Message-ID: <55B11C85.5070900@intel.com> (raw)
In-Reply-To: <20150723161644.GG27052@e104818-lin.cambridge.arm.com>
On 07/23/2015 09:16 AM, Catalin Marinas wrote:
> Anyway, if you want to keep the option of a full TLB flush for x86 on
> huge pages, I'm happy to repost a v2 with a separate
> flush_tlb_pmd_huge_page that arch code can define as it sees fit.
I think your patch is fine on x86. We need to keep an eye out for any
regressions, but I think it's OK.
next prev parent reply other threads:[~2015-07-23 16:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 17:13 [PATCH] mm: Flush the TLB for a single address in a huge page Catalin Marinas
2015-07-22 17:13 ` Catalin Marinas
2015-07-22 21:39 ` David Rientjes
2015-07-22 21:39 ` David Rientjes
2015-07-22 22:48 ` Catalin Marinas
2015-07-22 22:48 ` Catalin Marinas
2015-07-22 23:05 ` Dave Hansen
2015-07-22 23:05 ` Dave Hansen
2015-07-23 10:49 ` Catalin Marinas
2015-07-23 10:49 ` Catalin Marinas
2015-07-23 14:13 ` Andrea Arcangeli
2015-07-23 14:13 ` Andrea Arcangeli
2015-07-23 14:41 ` Dave Hansen
2015-07-23 14:41 ` Dave Hansen
2015-07-23 15:58 ` Andrea Arcangeli
2015-07-23 15:58 ` Andrea Arcangeli
2015-07-23 16:52 ` Dave Hansen
2015-07-23 16:52 ` Dave Hansen
2015-07-23 16:16 ` Catalin Marinas
2015-07-23 16:16 ` Catalin Marinas
2015-07-23 16:55 ` Dave Hansen [this message]
2015-07-23 16:55 ` Dave Hansen
2015-07-23 17:13 ` Andrea Arcangeli
2015-07-23 17:13 ` Andrea Arcangeli
2015-07-23 16:49 ` Catalin Marinas
2015-07-23 16:49 ` Catalin Marinas
2015-07-24 7:17 ` Martin Schwidefsky
2015-07-24 7:17 ` Martin Schwidefsky
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=55B11C85.5070900@intel.com \
--to=dave.hansen@intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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 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.