From: Gao Xiang <email@example.com>
To: firstname.lastname@example.org, email@example.com,
Cc: Matthew Wilcox <firstname.lastname@example.org>,
Gao Xiang <email@example.com>,
zhong jiang <firstname.lastname@example.org>, Chao Yu <email@example.com>,
Greg Kroah-Hartman <firstname.lastname@example.org>
Subject: Re: Tagged pointers in the XArray
Date: Wed, 29 Aug 2018 07:26:57 +0800 [thread overview]
Message-ID: <email@example.com> (raw)
On 2018/8/29 6:27, Matthew Wilcox wrote:
> I find myself caught between two traditions.
> On the one hand, the radix tree has been calling the page cache dirty &
> writeback bits "tags" for over a decade.
> On the other hand, using some of the bits _in a pointer_ as a tag has been
> common practice since at least the 1960s.
> https://en.wikipedia.org/wiki/Tagged_pointer and
Personally I think this topic makes sense. These two `tags' are totally
> EROFS wants to use tagged pointers in the radix tree / xarray. Right now,
> they're building them by hand, which is predictably grotty-looking.
> I think it's reasonable to provide this functionality as part of the
> XArray API, _but_ it's confusing to have two different things called tags.
> I've done my best to document my way around this, but if we want to rename
> the things that the radix tree called tags to avoid the problem entirely,
> now is the time to do it. Anybody got a Good Idea?
As Matthew pointed out, it is a good chance to rename one of them.
In addition to that, I am also looking forward to a better general
implementation to wrap up operations for all these tags and restrict the
number of tag bits
at compile time. It is also useful to mark its usage and clean up these
though the implementation could look a bit simple.
If you folks think the general tagged pointer is meaningless, please
ignore my words....
However according to my EROFS coding experience, code with different
kind of tagged
pointers by hand (directly use magic masks) will be in a mess, but it
unnecessary to introduce independent operations for each kind of tagged
In the end, I also hope someone interested in this topic and thanks in
next prev parent reply other threads:[~2018-08-28 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 22:27 Tagged pointers in the XArray Matthew Wilcox
2018-08-28 22:39 ` Randy Dunlap
2018-08-28 23:03 ` Matthew Wilcox
2018-08-28 23:09 ` Randy Dunlap
2018-08-28 23:24 ` Gao Xiang
2018-08-28 23:26 ` Gao Xiang [this message]
2018-08-29 16:17 ` Matthew Wilcox
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 NNTP newsgroup(s).