linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Small <tim@seoss.co.uk>
To: Wakko Warner <wakko@animx.eu.org>
Cc: tim@buttersideup.com, Christoph Hellwig <hch@infradead.org>,
	linux-scsi@vger.kernel.org, Jens Axboe <axboe@fb.com>,
	Borislav Petkov <bp@alien8.de>, Tim Waugh <tim@cyberelk.net>
Subject: Re: [PATCH 0/4] Fix performance burning or extracting audio etc. from multiple optical drives.
Date: Thu, 05 Nov 2015 09:36:32 +0000	[thread overview]
Message-ID: <563B2320.9070106@seoss.co.uk> (raw)
In-Reply-To: <20151105013806.GA21819@animx.eu.org>

On 05/11/15 01:38, Wakko Warner wrote:
> I tested on a system with 3 drives.  ejecting all drives didn't happen at
> the same time, but I think it's because they are different brands and one
> didn't have a disc in.  I did notice the leds coming on about the same time
> though.  eject -t on all drives happened at the same time.
> 
> The patch I used previously on 3.3.0 removed all mutex_lock and mutex_unlock
> lines from sr.c where as this patchset didn't.  I plan on trying to burn 3
> dvds to see if it works.
> 
> Thanks for your work on the patches.

No problem.  I haven't had any time to follow up (and probably won't for
the foreseeable - I've got far too much on at the moment unfortunately),
and the locking issues looked non-trivial unfortunately.

In my testing burning, and audio extracting etc. worked pretty
flawlessly IIRC, it was just the eject/load path which seemed to have
locking issues.

The test was just a shell scripts which ran:

while true ; do eject /dev/sr0 ; eject -T /dev/sr0 ; done

for every drive in the system simultaneously.

Hopefully it's a good start if someone wants to pick it up.  It's
possible that there's an easy way of leaving the old mutexes (or adding
more) around the relevant open/eject/load paths only, but I can't
remember the code now unfortunately.

If anyone wants to have a go, I think I can probably rig up about 8
drives to a testrig here, and will be happy to give it a test.

Tim.

  reply	other threads:[~2015-11-05 10:13 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
2015-11-05  1:38           ` Wakko Warner
2015-11-05  9:36             ` Tim Small [this message]
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=563B2320.9070106@seoss.co.uk \
    --to=tim@seoss.co.uk \
    --cc=axboe@fb.com \
    --cc=bp@alien8.de \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tim@buttersideup.com \
    --cc=tim@cyberelk.net \
    --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).