From: Jason Gunthorpe <jgg@ziepe.ca>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Freeing page tables through RCU
Date: Fri, 26 Feb 2021 10:42:00 -0400 [thread overview]
Message-ID: <20210226144200.GV2643399@ziepe.ca> (raw)
In-Reply-To: <20210225205820.GC2858050@casper.infradead.org>
On Thu, Feb 25, 2021 at 08:58:20PM +0000, Matthew Wilcox wrote:
> I'd like to hear better ideas than this.
You didn't like my suggestion to put a sleepable lock around the
freeing of page tables during flushing?
I still don't see how you convert the sleepable page walkers to use
rcu??
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: Freeing page tables through RCU
Date: Fri, 26 Feb 2021 10:42:00 -0400 [thread overview]
Message-ID: <20210226144200.GV2643399@ziepe.ca> (raw)
In-Reply-To: <20210225205820.GC2858050@casper.infradead.org>
On Thu, Feb 25, 2021 at 08:58:20PM +0000, Matthew Wilcox wrote:
> I'd like to hear better ideas than this.
You didn't like my suggestion to put a sleepable lock around the
freeing of page tables during flushing?
I still don't see how you convert the sleepable page walkers to use
rcu??
Jason
next prev parent reply other threads:[~2021-02-26 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 20:58 Freeing page tables through RCU Matthew Wilcox
2021-02-26 14:42 ` Jason Gunthorpe [this message]
2021-02-26 14:42 ` Jason Gunthorpe
2021-02-26 16:03 ` Matthew Wilcox
2021-02-26 16:03 ` Matthew Wilcox
2021-02-26 16:21 ` Jason Gunthorpe
2021-02-26 16:21 ` Jason Gunthorpe
2021-02-26 16:12 ` Gerald Schaefer
2021-02-26 16:12 ` Gerald Schaefer
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=20210226144200.GV2643399@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=willy@infradead.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.