From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] [SCSI] sr: fix multi-drive performance, remove BKL replacement
Date: Tue, 28 Feb 2012 09:00:01 -0600 [thread overview]
Message-ID: <1330441201.2822.126.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <20120228153244.70413d34@stein>
On Tue, 2012-02-28 at 15:32 +0100, Stefan Richter wrote:
> Commit 2a48fc0ab242 "block: autoconvert trivial BKL users to private
> mutex" and other commits at the time mechanically swapped BKL for
> per-driver global mutexes. If the sr driver is any indication, these
> replacements have still not been checked by anybody for their
> necessessity, removed where possible, or the sections they serialize
> reduced to a necessary minimum.
>
> The sr_mutex in particular very noticably degraded performance of
> CD-DA ripping with multiple drives in parallel. When several
> instances of "grip" are used with two or more drives, their GUIs
> became laggier, as did the KDE file manager GUI, and drive utilization
> was reduced. (During ripping, drive lights flicker instead of staying
> on most of the time.) IOW time to rip a stack of CDs was increased.
> I didn't measure this but it is highly noticeable.
>
> On the other hand, I don't see what state sr_mutex would protect.
> So I removed it entirely and that works fine for me.
>
I'm afraid you can't do that: The problem is that we have an entangled
set of reference counts that need to be taken and released atomically.
If we don't surround them with a mutex you get undefined results from
racing last release with new acquire. You can see this usage in sd.c.
The sr.c use case looks like bd_mutex would mediate ... but that's
because it doesn't use driver shutdown and has no power management
functions ... I think I have vague memories that someone is working on
pm for cdroms?
I don't think the mutex needs to be on the ioctls, though, which is
what's causing your performance problems, right?
James
next prev parent reply other threads:[~2012-02-28 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 14:32 Stefan Richter
2012-02-28 15:00 ` James Bottomley [this message]
2012-02-28 16:09 ` Stefan Richter
2012-02-28 16:16 ` James Bottomley
2012-02-28 16:42 ` Arnd Bergmann
2012-02-28 16:57 ` James Bottomley
2012-02-28 17:11 ` Stefan Richter
2012-02-28 16:22 ` Stefan Richter
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=1330441201.2822.126.camel@dabdike.int.hansenpartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®