From: Jeremy Linton <jlinton@tributary.com>
To: "Hannes Reinecke" <hare@suse.de>,
"\"Kai Mäkisara (Kolumbus)\"" <kai.makisara@kolumbus.fi>
Cc: James Bottomley <jbottomley@parallels.com>,
Kay Sievers <kay@vrfy.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] st: Do not rewind for SG_IO
Date: Mon, 3 Feb 2014 08:50:12 -0600 [thread overview]
Message-ID: <52EFACA4.6060001@tributary.com> (raw)
In-Reply-To: <52EE2F2D.1010300@suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2/2/2014 5:42 AM, Hannes Reinecke wrote:
> This is due to the strictly sequential design udev has. Essentially udev
> spawns a worker for every device which gets created (= udev receives a
> uevent for).
The part I fail to see in this explanation is why the nst/st/st*a/st*m/etc
handles are being treated as separate devices. They aren't. They are all the
same physical tape device, so why are the nst devices being handled separately
from the st ones?
Maybe the problem is that you have to many "workers" for the tape device.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJS76ykAAoJEL5i86xrzcy7MKMH/0upLuOBOJWzdOfKYq0WmIvZ
eIaaZG2vhckYeS2zZtim5uVFQDp5eTOirmjxfwSGzSTSAmNrQJwzZvBO/vA2/Kqk
wZSKXp/ZGZhw11+6Kg8f1EArQQwT/i3R6BKglLELFvZVvNOUg3KCnd6nE/4k7ysh
H3f6+6/Jb1wUA6h7a65BG7VBQlJ3HqVe01vYTrkb3eYW7IWfN0tX2FMdqYt2zon2
Yo6TRxhTE/dmqJhg8nLB+fA8rUwW7CYU/IX8nsKNn9lPaDdoJ6g22ozpJRrtEZZ+
lt/qL3VxfWu38z0GWhuKuOqY969bMlyaphY7bOgf7LY4osiC7OgarVoxSIgfP9E=
=pIPt
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-02-03 14:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 8:46 [PATCH] st: Do not rewind for SG_IO Hannes Reinecke
2014-01-31 16:36 ` Jeremy Linton
2014-01-31 16:43 ` Jeremy Linton
2014-02-01 14:06 ` Hannes Reinecke
2014-02-01 15:23 ` "Kai Mäkisara (Kolumbus)"
2014-02-02 11:42 ` Hannes Reinecke
2014-02-02 19:15 ` "Kai Mäkisara (Kolumbus)"
2014-02-03 6:55 ` Hannes Reinecke
2014-02-03 14:50 ` Jeremy Linton [this message]
2014-02-03 15:06 ` Hannes Reinecke
2014-02-03 15:08 ` Jeremy Linton
2014-02-03 20:51 ` Kay Sievers
2014-02-03 21:11 ` James Bottomley
2014-02-03 21:58 ` Jeremy Linton
2014-02-03 22:15 ` Kay Sievers
2014-02-03 22:26 ` Jeremy Linton
2014-02-06 13:10 ` Hannes Reinecke
2014-02-06 13:21 ` Martin K. Petersen
2014-02-06 13:26 ` Hannes Reinecke
2014-02-06 13:50 ` Martin K. Petersen
2014-02-06 14:38 ` James Bottomley
2014-02-06 15:13 ` Hannes Reinecke
2014-02-06 19:21 ` Douglas Gilbert
2014-02-03 21:16 ` Douglas Gilbert
2014-02-03 21:24 ` Kay Sievers
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=52EFACA4.6060001@tributary.com \
--to=jlinton@tributary.com \
--cc=hare@suse.de \
--cc=jbottomley@parallels.com \
--cc=kai.makisara@kolumbus.fi \
--cc=kay@vrfy.org \
--cc=linux-scsi@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.