From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jonathan Corbet <corbet@lwn.net>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] XArray
Date: Thu, 15 Nov 2018 21:47:30 -0500 [thread overview]
Message-ID: <20181116024730.GF20617@thunk.org> (raw)
In-Reply-To: <20181115160302.428a037b@lwn.net>
On Thu, Nov 15, 2018 at 04:03:02PM -0700, Jonathan Corbet wrote:
>
> Just FWIW, I was there, but I suspect I'll not be making an article out
> of it; quite a bit of the material was stuff that we've covered before.
> The video should be available in a week or two for those who want to
> catch up on the rest.
A good chunk of the contents of Matthew's talk can be found at:
https://lwn.net/Articles/745073/
https://www.kernel.org/doc/html/latest/core-api/xarray.html
Two important things that's not covered in these two links are:
1) Some future plans that Matthew has for making XArray even better
2) The use cases for which XArray is not (yet) ready.
Short version: Sparse arrays, hash tables, and other things where the
breadth of the keyspace that gets used is very wide relative to the
number of elements stored in the XArray. So if you need to store two
elements, one where the key is 0x0000000 and the other key is
0xffffff00, XArray might not be the best choice for you --- but maybe
that answer will change in a year or so --- see (1) above.
For more details, the video and slides should be available soon. :-)
Cheers,
- Ted
next prev parent reply other threads:[~2018-11-16 2:47 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 [this message]
2018-11-16 6:30 ` Matthew Wilcox
2018-11-14 22:56 ` William Kucharski
2018-11-15 1:07 ` 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=20181116024730.GF20617@thunk.org \
--to=tytso@mit.edu \
--cc=corbet@lwn.net \
--cc=ksummit-discuss@lists.linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).