From: Alasdair G Kergon <agk@redhat.com>
To: Milan Broz <gmazyland@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 9/9] dm crypt: sort writes
Date: Tue, 1 Apr 2014 21:15:45 +0100 [thread overview]
Message-ID: <20140401201545.GA24739@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <533AF8E0.2040907@gmail.com>
On Tue, Apr 01, 2014 at 07:35:28PM +0200, Milan Broz wrote:
> Btw if you don't like sysfs option for disabling this, it can be optional table parameter,
> there is already discard support implemented this way.
> (I could add this myself later... just need to find at least few hours
> of free time:)
But apart from using that option for benchmarking purposes, is there any reason
anyone would need to turn this off?
Do we know of any circumstances where the sorting causes a non-neglible
performance hit?
Alasdair
next prev parent reply other threads:[~2014-04-01 20:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 20:11 [PATCH 0/9] dm crypt: improve cpu scalability Mike Snitzer
2014-03-28 20:11 ` [PATCH 1/9] dm crypt: fix cpu hotplug crash by removing per-cpu structure Mike Snitzer
2014-03-28 20:11 ` [PATCH 2/9] block: use kmalloc alignment for bio slab Mike Snitzer
2014-03-28 20:11 ` [PATCH 3/9] dm crypt: use per-bio data Mike Snitzer
2014-03-28 20:11 ` [PATCH 4/9] dm crypt: use unbound workqueue for request processing Mike Snitzer
2014-03-28 20:11 ` [PATCH 5/9] dm crypt: don't allocate pages for a partial request Mike Snitzer
2014-03-28 20:11 ` [PATCH 6/9] dm crypt: avoid deadlock in mempools Mike Snitzer
2014-03-28 20:11 ` [PATCH 7/9] dm crypt: remove io_pool Mike Snitzer
2014-03-28 20:11 ` [PATCH 8/9] dm crypt: offload writes to thread Mike Snitzer
2014-04-01 16:27 ` Ondrej Kozina
2014-04-01 16:32 ` Mike Snitzer
2014-04-01 18:15 ` Mikulas Patocka
2014-04-01 18:23 ` Mike Snitzer
2014-04-02 6:55 ` Ondrej Kozina
2014-04-01 18:01 ` Mikulas Patocka
2014-04-01 19:08 ` Milan Broz
2014-03-28 20:11 ` [PATCH 9/9] dm crypt: sort writes Mike Snitzer
2014-03-29 8:11 ` Milan Broz
2014-03-31 12:39 ` Mike Snitzer
2014-03-31 23:37 ` Akira Hayakawa
2014-04-01 1:01 ` Mike Snitzer
2014-04-01 17:35 ` Milan Broz
2014-04-01 20:15 ` Alasdair G Kergon [this message]
2014-04-01 23:21 ` Akira Hayakawa
2014-04-02 3:19 ` Akira Hayakawa
2014-04-02 3:38 ` Mike Snitzer
2014-04-02 4:18 ` Akira Hayakawa
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=20140401201545.GA24739@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.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.