[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070504133645.7d053549.kristen.c.accardi@intel.com>
Date: Fri, 4 May 2007 13:36:45 -0700
From: Kristen Carlson Accardi <kristen.c.accardi@...el.com>
To: James Bottomley <James.Bottomley@...elEye.com>
Cc: jeff@...zik.org, linux-kernel@...r.kernel.org,
linux-scsi@...r.kernel.org, linux-ide@...r.kernel.org,
htejun@...il.com, akpm@...ux-foundation.org
Subject: Re: [patch 0/7] Asynchronous Notification for ATAPI devices (v2) -
resend
On Fri, 04 May 2007 15:30:03 -0500
James Bottomley <James.Bottomley@...elEye.com> wrote:
> On Fri, 2007-05-04 at 11:12 -0700, Kristen Carlson Accardi wrote:
> > This patch series implements Asynchronous Notification (AN) for SATA
> > ATAPI devices as defined in SATA 2.5 and AHCI 1.1 and higher. Drives
> > which support this feature will send a notification when new media is
> > inserted and removed, preventing the need for user space to poll for
> > new media. This support is exposed to user space via a flag that will
> > be set in /sys/block/sr*/capability_flags. If the flag is set, user
> > space can disable polling for the new media, and the genhd driver will
> > send a KOBJ_CHANGE event with the envp set to MEDIA_CHANGE_EVENT=1.
> >
> > Note that this patch only implements support for directly attached
> > drives - AN with drives attached to a port multiplier requires
> > additional changes.
>
> I seem to remember when this came up before, the observation was made
> that AENs occur for many more things than simple media change notices,
> so we should probably have a more generic AEN handling mechanism. Is
> there any plan to move in this direction
>
> James
>
In this implementation, we use kobject_uevent_env (vs. just
kobject_uevent in the original implementation) to send a KOBJ_CHANGE
with the enviroment value of MEDIA_CHANGE=1. For other asynchronous
events, you could still use KOBJ_CHANGE with a different env value.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists