From: Mikulas Patocka <mpatocka@redhat.com>
To: "Alasdair G. Kergon" <agk@redhat.com>, dm-devel@redhat.com
Subject: [PATCHES]: dm lock optimization
Date: Wed, 18 Apr 2012 23:03:33 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1204182249060.12984@file.rdu.redhat.com> (raw)
Hi
I placed dm lock optimization patches here
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 was able to measure performance improvement, although in a very specific
setup (it is unmeasurable with normal disks).
The setup to measure it is:
- two quad-core Opterons
- use ramdisk as a block device, leave it empty
- create 11 nested dm-linear mappings on it (so that each i/o passes
through 11 levels of dm-linear and then goes to the ramdisk)
- run fio with 8 threads, using direct-io to read 512-byte blocks
(time fio --rw=randread --size=1G --bsrange=512-512 --direct=1
--filename=/dev/mapper/dm-test --name=job1 --name=job2 --name=job3
--name=job4 --name=job5 --name=job6 --name=job7 --name=job8)
With this setup it can be measured that the patches help:
no patch (3.3 kernel): 68.9s
patch 1: 64.3s
patch 1,2: 52.3s
patch 1,2,3: 45.2s
patch 1,2,3,4: 41.2s
patch 1,2,3,4,5: 34.0s
Mikulas
next reply other threads:[~2012-04-19 3:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 3:03 Mikulas Patocka [this message]
2012-04-19 5:17 ` [PATCHES]: dm lock optimization Jun'ichi Nomura
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=Pine.LNX.4.64.1204182249060.12984@file.rdu.redhat.com \
--to=mpatocka@redhat.com \
--cc=agk@redhat.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.