From: Hannes Reinecke <hare@suse.de>
To: Tejun Heo <htejun@gmail.com>
Cc: James Bottomley <jbottomley@suse.de>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Richard Sharpe <realrichardsharpe@gmail.com>
Subject: Current plans for SDEV_EVT_* and friends
Date: Tue, 01 Feb 2011 15:55:14 +0100 [thread overview]
Message-ID: <4D481ED2.1060109@suse.de> (raw)
Hi Tejun,
seeing that you are moving the old SCSI / libata AEN handling over
to the new block-based workqueue, I was wondering what your plans
are with the remaining SDEV_EVT_* things.
Thing is I'm currently working on implementing proper Unit Attention
handling in the SCSI stack. For this I would need to have some field
off the scsi_device structure into which I can store information
about which events / event types are supported and which are activated.
So the existing bitmap approach with 'supported_events' would quite
a good starting point here, and it will even be useful to add
another one, eg 'enabled_events'.
And, of course, plan is to route appropriate events over to the
block workqueue by calling disk_check_events().
Unless you have other ideas/plans here ...
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2011-02-01 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 14:55 Hannes Reinecke [this message]
2011-02-01 14:59 ` Current plans for SDEV_EVT_* and friends Tejun Heo
2011-02-01 15:29 ` Hannes Reinecke
2011-02-01 15:29 ` Tejun Heo
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=4D481ED2.1060109@suse.de \
--to=hare@suse.de \
--cc=htejun@gmail.com \
--cc=jbottomley@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=realrichardsharpe@gmail.com \
/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