From: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: [PATCHES]: dm lock optimization
Date: Mon, 23 Apr 2012 19:56:52 +0900 [thread overview]
Message-ID: <4F953574.3000702@ce.jp.nec.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1204211215230.3269@file.rdu.redhat.com>
Hi Mikulas,
On 04/22/12 01:17, Mikulas Patocka wrote:
> I created new patches that use rcu instead of map_lock, so they address
> the issues you mentioned. Get the new patches here:
> http://people.redhat.com/mpatocka/patches/kernel/dm-lock-optimization/
>
> performance with new patches:
> no patch: 69.3
> patch 1: 54.0
> patch 1,2: 44.2
> patch 1,2,3: 39.8
> patch 1,2,3,4: 32.7
Thank you. I have 2 comments for the new patches.
synchronize_rcu could be put in dm_table_destroy() instead of __bind().
I think it's safer place to wait.
io_lock could be converted to SRCU.
I.e. something like:
On reader-side:
idx = srcu_read_lock(io_srcu);
if (!DMF_BLOCK_IO_FOR_SUSPEND)
split_and_process_bio();
srcu_read_unlock(io_srcu,idx);
In dm_suspend:
set_bit(DMF_BLOCK_IO_FOR_SUSPEND);
mb();
synchronize_srcu(io_srcu);
<from here, nobody will enter split_and_process_bio>
That makes dm-optimize-percpu-io-lock.patch simpler.
dm-optimize-take-io_lock-on-table-swap.patch may become simpler, too.
--
Jun'ichi Nomura, NEC Corporation
next prev parent reply other threads:[~2012-04-23 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 3:03 [PATCHES]: dm lock optimization Mikulas Patocka
2012-04-19 5:17 ` Jun'ichi Nomura
2012-04-21 16:17 ` Mikulas Patocka
2012-04-23 10:56 ` Jun'ichi Nomura [this message]
2012-05-02 2:17 ` Mikulas Patocka
2012-05-10 4:33 ` Jun'ichi Nomura
2012-05-18 6:37 ` Mikulas Patocka
2012-05-23 6:27 ` Jun'ichi Nomura
2012-04-23 13:14 ` Joe Thornber
2012-05-02 0:03 ` Mikulas Patocka
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=4F953574.3000702@ce.jp.nec.com \
--to=j-nomura@ce.jp.nec.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@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.