From: Nick Piggin <npiggin@suse.de>
To: Jan Kara <jack@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
fengguang.wu@intel.com
Subject: Re: [PATCH 1/3] radix-tree: Implement function radix_tree_gang_tag_if_tagged
Date: Tue, 16 Feb 2010 03:01:08 +1100 [thread overview]
Message-ID: <20100215160108.GT5723@laptop> (raw)
In-Reply-To: <1265929584-5080-2-git-send-email-jack@suse.cz>
On Fri, Feb 12, 2010 at 12:06:22AM +0100, Jan Kara wrote:
> Implement function for setting one tag if another tag is set
> for each item in given range.
>
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> include/linux/radix-tree.h | 3 ++
> lib/radix-tree.c | 82 ++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 85 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/radix-tree.h b/include/linux/radix-tree.h
> index c5da749..41fa087 100644
> --- a/include/linux/radix-tree.h
> +++ b/include/linux/radix-tree.h
> @@ -185,6 +185,9 @@ unsigned int
> radix_tree_gang_lookup_tag_slot(struct radix_tree_root *root, void ***results,
> unsigned long first_index, unsigned int max_items,
> unsigned int tag);
> +unsigned long radix_tree_gang_tag_if_tagged(struct radix_tree_root *root,
> + unsigned long first_index, unsigned long last_index,
> + unsigned int fromtag, unsigned int totag);
Really minor thing here, I think I called my equivalent something
like radix_tree_tag_set_if_tagged. We don't use tag/untag naming
but tag_set/tag_clear.
next prev parent reply other threads:[~2010-02-15 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 23:06 [RFC] [PATCH 0/3] Writeback livelock avoidance using page tags (v2) Jan Kara
2010-02-11 23:06 ` [PATCH 1/3] radix-tree: Implement function radix_tree_gang_tag_if_tagged Jan Kara
2010-02-15 16:01 ` Nick Piggin [this message]
2010-02-11 23:06 ` [PATCH 2/3] mm: Implement writeback livelock avoidance using page tagging Jan Kara
2010-02-12 19:39 ` Andrew Morton
2010-02-15 15:47 ` Jan Kara
2010-02-15 16:21 ` Nick Piggin
2010-02-15 16:24 ` Christoph Hellwig
2010-02-15 16:37 ` Nick Piggin
2010-02-15 19:57 ` Jan Kara
2010-02-16 14:19 ` Nick Piggin
2010-02-11 23:06 ` [PATCH 3/3] mm: Debugging of new livelock avoidance Jan Kara
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=20100215160108.GT5723@laptop \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.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 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.