All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Johan de Jong <jrdejong@gmail.com>
Cc: linux-kernel@vger.kernel.org, Thomas Schmitt <scdbackup@gmx.net>
Subject: Re: SCSI sr driver: parallel writes to optical serialized which hurts performance (sr_mutex)
Date: Sat, 5 Mar 2016 16:25:17 -0500	[thread overview]
Message-ID: <20160305212517.GA6030@animx.eu.org> (raw)
In-Reply-To: <CAHrxqh3pGJzVoxtgNgmbVSdwXSiH2cLGYpU4R2+eDEEfaHxi7A@mail.gmail.com>

Johan de Jong wrote:
> In the mean time I have applied and tested the 2013 patch by Otto Meta:
> 
> http://marc.info/?l=linux-scsi&m=135705061804384&w=2
> 
> which, in short, replaces mutex_lock(&sr_mutex) (global mutex), that
> was introduced in 2010 to replace lock_kernel(), by per-device mutexes
> and allowing concurrent ioctl(SG_IO) in different processes with
> different sr devices.

There seems to be a few patches floating around.  I've had one running on
3.3.0 for a long time w/o any issues.  I'm currently using the one from Tim
Small (Search for subject Fix performance burning or extracting audio etc.
from multiple optical drives.) on 4.x (where x is 3-4) and a 3.14.something
without any issues.

I still have the emails from Tim.  My current usage is 2 systems with 3
burners from the same source.

  parent reply	other threads:[~2016-03-05 21:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 11:00 SCSI sr driver: parallel writes to optical serialized which hurts performance (sr_mutex) Johan de Jong
2016-03-05 20:15 ` Johan de Jong
2016-03-05 20:47   ` Thomas Schmitt
2016-03-07 12:13     ` One Thousand Gnomes
2016-03-07 13:11       ` Thomas Schmitt
2016-03-05 21:25   ` Wakko Warner [this message]
2016-03-05 21:36     ` Johan de Jong
2016-03-06  2:06       ` Wakko Warner

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=20160305212517.GA6030@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=jrdejong@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scdbackup@gmx.net \
    /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.