From: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
To: dm-devel@redhat.com
Subject: Re: [PATCHES]: dm lock optimization
Date: Thu, 19 Apr 2012 14:17:14 +0900 [thread overview]
Message-ID: <4F8F9FDA.1000103@ce.jp.nec.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1204182249060.12984@file.rdu.redhat.com>
Hello Mikulas,
On 04/19/12 12:03, Mikulas Patocka wrote:
> http://people.redhat.com/mpatocka/patches/kernel/dm-lock-optimization/
>
> The patches remove cache-line bouncing from device mapper when multiple
> processors submit requests simultaneously.
I think the idea of optimization is nice.
From a quick look, however, I have some comments:
dm-optimize-no-irqsave-map-lock.patch:
- dm_get_live_table() is called from request_fn,
that can be called from in_interrupt context.
So the added BUG_ON will be triggered.
dm-optimize-percpu-io-lock.patch:
- The following existing mechanisms could be used:
* include/linux/rcupdate.h
* include/linux/lglock.h
(or extended if necessary).
dm-optimize-get_live_table_fast.patch:
- dm_lld_busy() can (theoretically, if dm-mpath is stacked)
be called from in_interrupt context and trigger the
BUG_ON.
--
Jun'ichi Nomura, NEC Corporation
next prev parent reply other threads:[~2012-04-19 5:17 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 [this message]
2012-04-21 16:17 ` Mikulas Patocka
2012-04-23 10:56 ` Jun'ichi Nomura
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=4F8F9FDA.1000103@ce.jp.nec.com \
--to=j-nomura@ce.jp.nec.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.