From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <matthew.r.wilcox@intel.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Matthew Wilcox <willy@linux.intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 0/8] Support multi-order entries in the radix tree
Date: Thu, 21 Jan 2016 16:28:41 -0800 [thread overview]
Message-ID: <20160121162841.9116af529b6ce0ce6b00aefc@linux-foundation.org> (raw)
In-Reply-To: <1453213533-6040-1-git-send-email-matthew.r.wilcox@intel.com>
On Tue, 19 Jan 2016 09:25:25 -0500 Matthew Wilcox <matthew.r.wilcox@intel.com> wrote:
> Before diving into the important modifications, I add Andrew Morton's
> radix tree test harness to the tree in patches 1 & 2. It was absolutely
> invaluable in catching some of my bugs.
(cc Shuah for tools/testing/selftests)
Cool, thanks for doing that. I think a lot of this came from Nick Piggin
a long time ago, but I was bad about attributing it.
I wonder how good the coverage is - I don't think it's been seriously
updated since 2010 and presumably it isn't hitting on later-added
features. Doesn't matter - someone will add things later if needed.
And when I bug them to update the test harness ;)
I don't think it will link on my system - I have no liburcu by default.
I wonder if this will break lots of people's "make kselftest".
I'll get all this into -next tomorrow. Hopefully Ross will have time
to go through it sometime (non-urgently - it's 4.6 stuff).
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <matthew.r.wilcox@intel.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Matthew Wilcox <willy@linux.intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 0/8] Support multi-order entries in the radix tree
Date: Thu, 21 Jan 2016 16:28:41 -0800 [thread overview]
Message-ID: <20160121162841.9116af529b6ce0ce6b00aefc@linux-foundation.org> (raw)
In-Reply-To: <1453213533-6040-1-git-send-email-matthew.r.wilcox@intel.com>
On Tue, 19 Jan 2016 09:25:25 -0500 Matthew Wilcox <matthew.r.wilcox@intel.com> wrote:
> Before diving into the important modifications, I add Andrew Morton's
> radix tree test harness to the tree in patches 1 & 2. It was absolutely
> invaluable in catching some of my bugs.
(cc Shuah for tools/testing/selftests)
Cool, thanks for doing that. I think a lot of this came from Nick Piggin
a long time ago, but I was bad about attributing it.
I wonder how good the coverage is - I don't think it's been seriously
updated since 2010 and presumably it isn't hitting on later-added
features. Doesn't matter - someone will add things later if needed.
And when I bug them to update the test harness ;)
I don't think it will link on my system - I have no liburcu by default.
I wonder if this will break lots of people's "make kselftest".
I'll get all this into -next tomorrow. Hopefully Ross will have time
to go through it sometime (non-urgently - it's 4.6 stuff).
next prev parent reply other threads:[~2016-01-22 0:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 14:25 [PATCH 0/8] Support multi-order entries in the radix tree Matthew Wilcox
2016-01-19 14:25 ` Matthew Wilcox
2016-01-19 14:25 ` [PATCH 1/8] radix-tree: Add an explicit include of bitops.h Matthew Wilcox
2016-01-19 14:25 ` Matthew Wilcox
2016-01-19 14:25 ` [PATCH 2/8] radix tree test harness Matthew Wilcox
2016-01-19 14:25 ` Matthew Wilcox
2016-01-26 23:44 ` Andrew Morton
2016-01-26 23:44 ` Andrew Morton
2016-01-27 3:20 ` Matthew Wilcox
2016-01-27 3:20 ` Matthew Wilcox
2016-01-19 14:25 ` [PATCH 3/8] radix-tree: Cleanups Matthew Wilcox
2016-01-19 14:25 ` Matthew Wilcox
2016-01-19 14:25 ` [PATCH 4/8] radix_tree: Convert some variables to unsigned types Matthew Wilcox
2016-01-19 14:25 ` Matthew Wilcox
2016-01-19 14:25 ` [PATCH 5/8] radix_tree: Tag all internal tree nodes as indirect pointers Matthew Wilcox
2016-01-19 14:25 ` Matthew Wilcox
2016-01-19 14:25 ` [PATCH 6/8] radix_tree: Loop based on shift count, not height Matthew Wilcox
2016-01-19 14:25 ` Matthew Wilcox
2016-01-19 14:25 ` [PATCH 7/8] radix_tree: Add support for multi-order entries Matthew Wilcox
2016-01-19 14:25 ` Matthew Wilcox
2016-01-19 14:25 ` [PATCH 8/8] radix_tree: Add radix_tree_dump Matthew Wilcox
2016-01-19 14:25 ` Matthew Wilcox
2016-01-22 0:28 ` Andrew Morton [this message]
2016-01-22 0:28 ` [PATCH 0/8] Support multi-order entries in the radix tree Andrew Morton
2016-02-24 20:24 ` Ross Zwisler
2016-02-24 20:24 ` Ross Zwisler
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=20160121162841.9116af529b6ce0ce6b00aefc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.r.wilcox@intel.com \
--cc=ross.zwisler@linux.intel.com \
--cc=shuahkh@osg.samsung.com \
--cc=willy@linux.intel.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 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.