From: James Bottomley <James.Bottomley@SteelEye.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux-SCSI <linux-scsi@vger.kernel.org>,
akpm@linux-foundation.org
Subject: Re: [PATCH v4 0/2] [SCSI] Asynchronous event notification infrastructure
Date: Mon, 29 Oct 2007 10:43:44 -0500 [thread overview]
Message-ID: <1193672624.3383.25.camel@localhost.localdomain> (raw)
In-Reply-To: <15624bab8dc0206e384ac8314257a900e60127c1.1193668176.git.jeff@garzik.org>
On Mon, 2007-10-29 at 10:42 -0400, Jeff Garzik wrote:
> This is the next revision of the SCSI event notification infrastructure
> patchset, enabling SATA Asynchronous Notification ("AN") for CD/DVD
> devices that support it.
>
> For devices that support SATA AN (only very recent ones do), this means
> that HAL and other userspace utilities no longer need to repeatedly poll
> the CD/DVD device to determine if the user has changed the media.
>
> This revision takes into account James' comments from earlier today,
> modulo the following notes:
>
> * I think the various event attributes should always be present,
> for all devices at all times. If various events are not supported,
> the attribute will of course return zero (false, not supported).
Actually, I don't think so. We have precedent for this in the transport
classes: if a device doesn't support a feature, we don't export the flag
for that feature through sysfs. This allows not only feature control,
but an immediate view of the device capabilities simply by viewing the
sysfs directory.
I think this functionality is very easy to layer in, so there's no
reason not to do it.
> * I do not think this work should be blocked behind a revamp
> of the attribute group interface.
Assuming gregkh or kay ack, it won't be.
> * I was slack and did not bother to implement the 'set' operation
> for the attributes. This can easily be done at a later time in a
> separate patch. It is not a merge stopper to have the driver
> exclusively control the event mask, rather than driver+sysfs.
James
next prev parent reply other threads:[~2007-10-29 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 14:42 [PATCH v4 0/2] [SCSI] Asynchronous event notification infrastructure Jeff Garzik
2007-10-29 14:42 ` [PATCH v4 1/2] SCSI: " Jeff Garzik
2007-10-29 15:51 ` James Bottomley
2007-10-29 16:07 ` Jeff Garzik
2007-10-29 16:17 ` James Bottomley
2007-10-29 16:29 ` Jeff Garzik
2007-10-29 17:01 ` James Bottomley
2007-10-29 21:31 ` [PATCH v5 0/2] SCSI asynchronous event notification API Jeff Garzik
2007-10-29 21:31 ` [PATCH v5 1/2] SCSI: add " Jeff Garzik
2007-10-29 21:31 ` [PATCH v5 2/2] libata: Utilize new SCSI event infrastructure Jeff Garzik
2007-10-29 14:42 ` [PATCH v4 " Jeff Garzik
2007-10-29 15:43 ` James Bottomley [this message]
2007-10-29 15:58 ` [PATCH v4 0/2] [SCSI] Asynchronous event notification infrastructure Jeff Garzik
2007-10-29 16:10 ` James Bottomley
2007-10-29 16:24 ` Jeff Garzik
2007-10-29 16:34 ` James Bottomley
2007-10-29 16:48 ` Jeff Garzik
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=1193672624.3383.25.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).