From: Matthew Wilcox <willy6545@gmail.com>
To: William Kucharski <william.kucharski@oracle.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] XArray
Date: Wed, 14 Nov 2018 17:07:43 -0800 [thread overview]
Message-ID: <CAFhKne97iW1S=V5ECqJYDQEPDxNc+RTUnOTR8+1+=2or+VLFHg@mail.gmail.com> (raw)
In-Reply-To: <0AB62846-5A8B-4487-A4F9-1322B2B6E19B@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
I decided to leave that out of today's talk (in this timeslot; it was
briefly discussed in Christoph & Mike's hugepage slot during the
performance miniconf).
I should have patches soon to implement that -- the problem is not on the
XArray side, but on the page cache side. Unless there's a bug, of course,
and DAX is the canary in the coal-mine here.
On Wed., Nov. 14, 2018, 15:46 William Kucharski <
william.kucharski@oracle.com wrote:
>
>
> > On Nov 13, 2018, at 11:02 AM, Matthew Wilcox <willy6545@gmail.com>
> wrote:
> >
> > Now that the XArray is in, it's time to make use of it. I've got a git
> tree which converts every current user of the radix tree to the XArray as
> well as converting some users of the IDA to the XArray.
> >
> > The XArray may also be a great replacement for a list_head in your data
> structure.
> >
> > I can also talk about currently inappropriate uses for the XArray and
> what I might do in future to make the XArray useful for more users.
>
> I hope you'll also cover multi-order usage, e.g. for huge page size
> support in the page cache.
>
> Thanks!
> -- Bill
[-- Attachment #2: Type: text/html, Size: 1560 bytes --]
prev parent reply other threads:[~2018-11-15 1:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 18:02 [Ksummit-discuss] [TOPIC] XArray Matthew Wilcox
2018-11-13 22:31 ` Theodore Y. Ts'o
2018-11-14 10:02 ` Linus Walleij
2018-11-14 16:29 ` Theodore Y. Ts'o
2018-11-15 23:03 ` Jonathan Corbet
2018-11-16 2:47 ` Theodore Y. Ts'o
2018-11-16 6:30 ` Matthew Wilcox
2018-11-14 22:56 ` William Kucharski
2018-11-15 1:07 ` Matthew Wilcox [this message]
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='CAFhKne97iW1S=V5ECqJYDQEPDxNc+RTUnOTR8+1+=2or+VLFHg@mail.gmail.com' \
--to=willy6545@gmail.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=william.kucharski@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).