From: Tim Small <tim@seoss.co.uk>
To: Julian Calaby <julian.calaby@gmail.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Cc: Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@infradead.org>,
tim@buttersideup.com, Wakko Warner <wakko@animx.eu.org>
Subject: Re: [PATCH 0/4] Fix performance burning or extracting audio etc. from multiple optical drives.
Date: Thu, 27 Nov 2014 07:08:13 +0000 [thread overview]
Message-ID: <5476CDDD.3040501@seoss.co.uk> (raw)
In-Reply-To: <CAGRGNgWCdbqTjbBu9fbwWHe9AHK04vO_5HAwyo4rH80PyUQKbA@mail.gmail.com>
On 26/11/14 23:01, Julian Calaby wrote:
> As you're playing with locks, I assume you're running with LOCKDEP
> enabled? If not, that might tell you what's going on.
Hi,
Sorry - I should have said - LOCKDEP is on, and not reporting anything...
Cheers,
Tim.
next prev parent reply other threads:[~2014-11-27 7:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 13:25 Very slow throughput when using cdparanoia on two SATA CDROM drives with /dev/sr but not /dev/sg Tim Small
2014-11-07 21:37 ` Wakko Warner
2014-11-20 6:34 ` Christoph Hellwig
2014-11-20 8:16 ` Tim Small
2014-11-21 10:02 ` Christoph Hellwig
2014-11-25 14:09 ` [PATCH 0/4] Fix performance burning or extracting audio etc. from multiple optical drives Tim Small
2014-11-25 16:26 ` Christoph Hellwig
2014-11-25 16:30 ` Jens Axboe
2014-11-25 16:32 ` Christoph Hellwig
2014-11-25 16:36 ` Jens Axboe
2014-11-26 15:33 ` Tim Small
2014-11-26 20:34 ` Tim Small
2014-11-26 23:01 ` Julian Calaby
2014-11-27 7:08 ` Tim Small [this message]
2015-11-05 1:38 ` Wakko Warner
2015-11-05 9:36 ` Tim Small
2014-11-25 14:09 ` [PATCH 1/4] enable cdrom_ioctl() to be called without holding ex-BKL mutexes Tim Small
2014-11-25 14:09 ` [PATCH 2/4] Remove ex-BKL lock from ioctl path; fix simultaneous record on >1 drive Tim Small
2014-11-25 14:09 ` [PATCH 3/4] " Tim Small
2014-11-25 14:09 ` [PATCH 4/4] " Tim Small
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=5476CDDD.3040501@seoss.co.uk \
--to=tim@seoss.co.uk \
--cc=axboe@fb.com \
--cc=hch@infradead.org \
--cc=julian.calaby@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tim@buttersideup.com \
--cc=wakko@animx.eu.org \
/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;
as well as URLs for NNTP newsgroup(s).