All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dongmao Zhang <dmzhang@suse.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 1/1] improve the performance of	dm-log-userspace
Date: Wed, 11 Dec 2013 16:01:50 +0800	[thread overview]
Message-ID: <52A81BEE.2030600@suse.com> (raw)
In-Reply-To: <CFEF63AA-BBCD-4D61-A43C-9D785E45182C@redhat.com>

hi, brassow

   Yes, I had submited a patch lvm-devel.

http://www.redhat.com/archives/lvm-devel/2013-November/msg00093.html.

please review.

I should have add a patch version indicator.







于 2013年12月11日 09:17, Brassow Jonathan 写道:
> Looks good.  Did you happen to post the accompanying userspace patches?  If you pass those along, I will review that also and test them together.  Once that's done, I will ACK.
>
>   brassow
>
> On Dec 3, 2013, at 11:35 PM, dongmao zhang wrote:
>
>> modified workqueue calls on  Hayakawa's comments
>>
>> In the cluster evironment, cluster write has poor performance.
>
> </snip>
>
>> 	spinlock_t flush_lock;
>> 	struct list_head mark_list;
>> 	struct list_head clear_list;
>> +
>> +	/*work queue for flush clear region*/
>
> Use spaces after /* and before */
>
>> +	struct workqueue_struct *dmlog_wq;
>> +	struct delayed_work flush_log_work;
>> +	atomic_t sched_flush;
>> +	uint32_t integrated_flush;
>> };
>
> </snip>
>
>> 	devices_rdata = kzalloc(devices_rdata_size, GFP_KERNEL);
>> 	if (!devices_rdata) {
>> 		DMERR("Failed to allocate memory for device information");
>> @@ -246,6 +268,20 @@ static int userspace_ctr(struct dm_dirty_log *log, struct dm_target *ti,
>> 			DMERR("Failed to register %s with device-mapper",
>> 			      devices_rdata);
>> 	}
>> +
>> +
>
> Extra newline...
>
> The rest looks good.  (Cosmetic issues like this wouldn't prevent my ACK though.)
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2013-12-11  8:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04  5:35 [PATCH 1/1] improve the performance of dm-log-userspace dongmao zhang
2013-12-11  1:17 ` Brassow Jonathan
2013-12-11  8:01   ` Dongmao Zhang [this message]
2014-01-06  5:06     ` Dongmao Zhang
2014-01-13  1:18       ` Brassow Jonathan
  -- strict thread matches above, loose matches on Subject: below --
2013-11-21  8:19 dongmao zhang
2013-11-21 10:26 ` Akira Hayakawa
2013-11-26 10:12   ` Dongmao Zhang
     [not found] <yes>
2013-09-10  9:25 ` [PATCH 0/1] ideas to improve the write performance of cluster dm-raid1 dongmao zhang
2013-09-10  9:25   ` [PATCH 1/1] improve the performance of dm-log-userspace dongmao zhang
2013-10-28 10:07 ` [PATCH 0/1] patches to improve cluster raid1 performance [V3] dongmao zhang
2013-10-28 10:07   ` [PATCH 1/1] improve the performance of dm-log-userspace dongmao zhang
2013-10-30  1:35     ` Brassow Jonathan

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=52A81BEE.2030600@suse.com \
    --to=dmzhang@suse.com \
    --cc=dm-devel@redhat.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.