[dm-crypt] dm-crypt performance
vgoyal at redhat.com
Thu Mar 28 21:38:08 CET 2013
On Thu, Mar 28, 2013 at 12:44:43PM -0700, Tejun Heo wrote:
> On Thu, Mar 28, 2013 at 03:33:43PM -0400, Vivek Goyal wrote:
> > I am curious why out of order bio is a problem. Doesn't the elevator
> > already merge bio's with existing requests and if merging does not
> > happen then requests are sorted in order. So why ordering is not
> > happening properly with dm-crypt. What additional info dm-crypt has
> > that it can do better ordering than IO scheduler.
> Hmmm... well, for one, it doesn't only change ordering. It also
> changes the timings. Before iosched would get contiguous stream of
> IOs when the queue gets unplugged (BTW, how does dm crypt handling
> plugging? If not handled properly, it could definitely affect a lot
> of things.) With multiple threads doing encryption in the middle, the
> iosched could get scattered IOs which could easily span multiple
> millisecs. Even if context tagging was done properly, it could easily
> lead to much less efficient IO patterns to hardware.
> Keeping IO order combined with proper plug handling would not only
> keep the ordering constant but also the relative timing of events,
> which is an important factor when scheduling IOs.
If timing of unordered IO is an issue, then dm-crypt can try
to batch IO submission using blk_start_plug()/blk_finish_plug(). That way
dm-crypt can batch bio and control submission and there should not
be a need to put specific ordering logic in dm-crypt.
So if there are multiple threads doing crypto, they end up submitting
bio after crypto operation or queue it somewhere and ther is single
If compltion of crypto is an issue, then I think it is very hard to
determine whether extra waiting helps with throughput or hurts. If
dm-crypt can decide that somehow, then I guess they can just try
to do batch submission of IO from various crypto threads and see
if it helps with performance. (At some point of time, submitter
thread will become a bottleneck).
> > CFQ might seeing more performance hit because we maintain per
> > process queues and kernel threads might not be sharing the IO context
> > (i am not sure). So if all the crypto threads can share the IO
> > context, atleast it will make sure all IO from them goes into a
> > single queue.
> Right, this is important too although I fail to see how workqueue
> vs. custom dispatch would make any difference here. dm-crypt should
> definitely be using bio_associate_current().
Agreed. bio_associate_current() will atleast help keeping all bios
of single context in single queue and promote more merging (if submission
happens in right time frame).
More information about the dm-crypt