All of lore.kernel.org
 help / color / mirror / Atom feed
From: Etienne DADA <dadabox@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: scsi/sr - Impossible to write CDs/DVDs simultaneously (since BKL removal ?)
Date: Sun, 30 Oct 2011 02:05:53 +0200	[thread overview]
Message-ID: <4EAC94E1.9030603@gmail.com> (raw)

When burning multiple CDs/DVDs in parallel with multiple SATA drives, 
you can notice that :
- the process is abnormaly slow using cdrskin or wodim (top shows lots 
of I/O wait),
- the discs are burnt one after each other using cdrecord.

A simpler way to touch the problem is running :
$ eject /dev/sr0 & eject /dev/sr1
drives ejects sequentialy, rather than simultaneously as we were used to.


I think this problem arose after the Big Kernel Lock removal.
As far as I can understand the new "sr_mutex" private mutex in 
drivers/scsi/sr.c generates a per-driver locking, where a per-device 
locking would have been far better. I also think other drivers like sg 
are impacted by the same problem.

I am absolutely unable to arrange this, and would be pleased if someone 
competent could work on this.


Please CC me when answering as I'm not subscribing to the list.

Yours,
Étienne DADA

                 reply	other threads:[~2011-10-30  0:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4EAC94E1.9030603@gmail.com \
    --to=dadabox@gmail.com \
    --cc=linux-kernel@vger.kernel.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 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.