All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Steve Capper <steve.capper@arm.com>,
	linux-mm@kvack.org, David Hildenbrand <david@redhat.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH v2] tlb: hugetlb: Add more sizes to tlb_remove_huge_tlb_entry
Date: Wed, 6 Apr 2022 13:21:24 +0200	[thread overview]
Message-ID: <20220406112124.GD2731@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <cd075502-0c44-2c38-90fd-869966651d50@arm.com>

On Wed, Mar 30, 2022 at 07:34:16PM +0530, Anshuman Khandual wrote:

> I am wondering whether this should take care of gigantic PGDIR_SIZE
> based HugeTLB pages as well ? Although, it will require another new
> helper tlb_flush_pgd_range(). Any thoughts ?

I'm thinking that should be straight forward, you need a ->cleared_pgds
along with all that, but yeah.


  reply	other threads:[~2022-04-06 11:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 16:52 [PATCH] tlb: hugetlb: Add arm64 contiguous hint awareness Steve Capper
2022-03-23 18:30 ` Catalin Marinas
2022-03-24 14:33 ` Peter Zijlstra
2022-03-24 14:35   ` Steve Capper
2022-03-24 15:58     ` Peter Zijlstra
2022-03-24 16:11       ` Steve Capper
2022-03-30 11:25         ` [PATCH v2] tlb: hugetlb: Add more sizes to tlb_remove_huge_tlb_entry Steve Capper
2022-03-30 12:05           ` David Hildenbrand
2022-03-30 14:04           ` Anshuman Khandual
2022-04-06 11:21             ` Peter Zijlstra [this message]
2022-04-04  6:07           ` Anshuman Khandual
2022-04-05 14:26           ` Catalin Marinas
2022-04-06 11:40           ` Peter Zijlstra
2022-04-06 12:05           ` Will Deacon

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=20220406112124.GD2731@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=steve.capper@arm.com \
    --cc=will@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.