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>,
Doug Gilbert <dgilbert@interlog.com>
Subject: Re: [PATCH] st: Do not rewind for SG_IO
Date: Mon, 3 Feb 2014 09:08:23 -0600 [thread overview]
Message-ID: <52EFB0E7.3000504@tributary.com> (raw)
In-Reply-To: <52EFB06C.8010101@suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2/3/2014 9:06 AM, Hannes Reinecke wrote:
> That's due to udev. Udev is getting events for each device it should create
> a device node for. So for 'st' it'll get a series of events for 'stX', and
> another series of events for 'nstX'. Udev will treat each of these events
> separately, with distinct worker programs handling them. Each of those
> workers run fully asynchronous and cannot access information from other
> workers.
So whats wrong with the simple solution? You throw the ones for st away, and
create the st handles from the nst worker.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJS77DnAAoJEL5i86xrzcy7j+cH/24oncr+DN1yZ4ReXk3i8QHx
LpI83UgP9EAvvcHJb5Op3IQtojccda1rYmecMS8qLYV0IX33lJg6UXbhkNS/skkR
gFbPdsD/27JqJZvCU02U+ET0zfO5XH833UCRKOsqoA/GMeikLAaUKPV5t65eyCHh
Qy4CYr4Gve9AxMhV9n00IdadOL5NoH/aO+Qb916zeJ2dUng5TUDqQ3WzdlQQdhD5
ObReHBnTBXlsWQdZL2VakP6gEX2ijiZ09GOIeSf1rKz/974OAudmzLsVjF4BwqTA
5JzqQXezYO2CZ8zkiuCCuiuXEwjv3f62rCuqzi5lQByFGDpvJNMZDAU9GjTn9Z8=
=ELYk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-02-03 15:08 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
2014-02-03 15:06 ` Hannes Reinecke
2014-02-03 15:08 ` Jeremy Linton [this message]
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=52EFB0E7.3000504@tributary.com \
--to=jlinton@tributary.com \
--cc=dgilbert@interlog.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.