From: NeilBrown <neilb@suse.de>
To: Shaohua Li <shli@kernel.org>
Cc: linux-raid@vger.kernel.org, tj@kernel.org, dan.j.williams@gmail.com
Subject: Re: [patch v3 2/5] raid5: fix stripe release order
Date: Wed, 28 Aug 2013 16:37:27 +1000 [thread overview]
Message-ID: <20130828163727.76de453d@notabene.brown> (raw)
In-Reply-To: <20130828062905.GA17163@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2973 bytes --]
On Wed, 28 Aug 2013 14:29:05 +0800 Shaohua Li <shli@kernel.org> wrote:
> On Wed, Aug 28, 2013 at 01:41:50PM +1000, NeilBrown wrote:
> >
> > > +struct llist_node *llist_reverse_order(struct llist_node *head)
> > > +{
> > > + struct llist_node *second, *third;
> > > +
> > > + if (head == NULL || head->next == NULL)
> > > + return head;
> > > + second = head->next;
> > > + head->next = NULL;
> > > +
> > > + do {
> > > + third = second->next;
> > > + second->next = head;
> > > +
> > > + head = second;
> > > + second = third;
> > > + } while (second);
> > > +
> > > + return head;
> > > +}
> > > +EXPORT_SYMBOL_GPL(llist_reverse_order);
> >
> > This is somewhat longer that necessary.
> >
> > struct llist_node *llist_reverse_order(struct llist_node *head)
> > {
> > struct llist_node *new_head = NULL;
> >
> > while (head) {
> > struct llist_node *tmp = head;
> > head = head->next;
> > tmp->next = new_head;
> > new_head = tmp;
> > }
> >
> > return new_head;
> > }
> >
> > I think that is short enough to just open-code in the top of
> > release_stripe_list.
> >
> > Are you OK with that?
>
> It's ok. Other patches can still apply with hunks.
>
> Subject: raid5: fix stripe release order
>
> patch "make release_stripe lockless" changes the order stripes are released.
> Originally I thought block layer can take care of request merge, but it appears
> there are still some requests not merged. It's easy to fix the order.
>
> Signed-off-by: Shaohua Li <shli@fusionio.com>
> ---
> drivers/md/raid5.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> Index: linux/drivers/md/raid5.c
> ===================================================================
> --- linux.orig/drivers/md/raid5.c 2013-08-28 13:51:39.586914255 +0800
> +++ linux/drivers/md/raid5.c 2013-08-28 13:53:25.429582150 +0800
> @@ -239,6 +239,20 @@ static void __release_stripe(struct r5co
> do_release_stripe(conf, sh);
> }
>
> +static struct llist_node *llist_reverse_order(struct llist_node *head)
> +{
> + struct llist_node *new_head = NULL;
> +
> + while (head) {
> + struct llist_node *tmp = head;
> + head = head->next;
> + tmp->next = new_head;
> + new_head = tmp;
> + }
> +
> + return new_head;
> +}
> +
> /* should hold conf->device_lock already */
> static int release_stripe_list(struct r5conf *conf)
> {
> @@ -247,6 +261,7 @@ static int release_stripe_list(struct r5
> struct llist_node *head;
>
> head = llist_del_all(&conf->released_stripes);
> + head = llist_reverse_order(head);
> while (head) {
> sh = llist_entry(head, struct stripe_head, release_list);
> head = llist_next(head);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Applied, thanks.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-08-28 6:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 9:50 [patch v3 0/5] raid5: make stripe handling multi-threading Shaohua Li
2013-08-27 9:50 ` [patch v3 1/5] raid5: make release_stripe lockless Shaohua Li
2013-08-28 14:04 ` Tejun Heo
2013-08-28 14:29 ` Shaohua Li
2013-08-28 14:30 ` Tejun Heo
2013-08-27 9:50 ` [patch v3 2/5] raid5: fix stripe release order Shaohua Li
2013-08-28 3:41 ` NeilBrown
2013-08-28 6:29 ` Shaohua Li
2013-08-28 6:37 ` NeilBrown [this message]
2013-08-27 9:50 ` [patch v3 3/5] raid5: offload stripe handle to workqueue Shaohua Li
2013-08-28 3:53 ` NeilBrown
2013-08-28 6:30 ` Shaohua Li
2013-08-28 6:56 ` NeilBrown
2013-08-27 9:50 ` [patch v3 4/5] raid5: sysfs entry to control worker thread number Shaohua Li
2013-08-27 9:50 ` [patch v3 5/5] raid5: only wakeup necessary threads Shaohua Li
2013-08-28 4:13 ` NeilBrown
2013-08-28 6:31 ` Shaohua Li
2013-08-28 6:59 ` NeilBrown
2013-08-29 7:40 ` Shaohua Li
2013-09-02 0:45 ` NeilBrown
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=20130828163727.76de453d@notabene.brown \
--to=neilb@suse.de \
--cc=dan.j.williams@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.org \
--cc=tj@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.