From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] XArray for 4.20
Date: Sun, 28 Oct 2018 12:13:45 -0700 [thread overview]
Message-ID: <20181028191345.GA28520@bombadil.infradead.org> (raw)
In-Reply-To: <CAHk-=whquhQQY38WRKYsi-_a2vD=_22EPEnfVj4+APEjZPAkMw@mail.gmail.com>
On Sun, Oct 28, 2018 at 11:50:19AM -0700, Linus Torvalds wrote:
> On Tue, Oct 23, 2018 at 1:08 PM Matthew Wilcox <willy@infradead.org> wrote:
> <
> > Please consider pulling the XArray patch set.
>
> Pulled.
Thanks!
> I took the more recent version of yours, because by the time I
> actually had time to review this thing for pulling, even the recent
> version had been in linux-next for a week.
>
> Of course, I don't think linux-next has been updated, so it's all
> moot, but the point is that I didn't get the feeling that it was all
> some very recent code.
>
> I do like how the conversions look, with the code in some cases
> notably simpler. And it looks like at least one of the conflicts
> (fs/dax.c) was due to a bug-fix to the old code where your simpler
> xarray replacement didn't have the problem.
Yes, that's right. It turned out to be a problem for any multiorder
radix tree user, and that was a consequence of how the radix tree API
worked for multiorder entries. The XArray API just works better for
multiorder entries.
> NOTE! I did get some conflicts with other stuff, and while the
> conflict resolution all looked pretty straightforward, this does want
> looking at.
>
> Particularly the mm/workingset.c code.
I've been rebasing the xarray-conv branch on your tree pretty regularly
this week, so I have a fairly good idea how I think it should look.
I'll check to see if you & I have the same thoughts when you push it out.
> It's still undergoing my build tests to verify my merge, but that
> should be completed soon. I'll do a basic boot test too due to the
> core nature of these changes, but assuming it all passes I'll push
> this out within the next 30 minutes and would appreciate people giving
> it a second look for verification.
Thank you.
next prev parent reply other threads:[~2018-10-28 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 20:08 Matthew Wilcox
2018-10-24 3:29 ` Matthew Wilcox
2018-10-28 18:50 ` Linus Torvalds
2018-10-28 19:13 ` Matthew Wilcox [this message]
2018-10-28 19:21 ` Linus Torvalds
2018-10-28 19:27 ` Matthew Wilcox
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=20181028191345.GA28520@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®