From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: scsi <linux-scsi@vger.kernel.org>, David Zeuthen <david@fubar.dk>,
kristen accardi <kaccardi@gmail.com>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: [PATCH] fix media change events for polled devices
Date: Wed, 19 Mar 2008 20:25:57 -0500 [thread overview]
Message-ID: <1205976357.11527.63.camel@localhost.localdomain> (raw)
In-Reply-To: <1205975933.5498.11.camel@lov.site>
On Thu, 2008-03-20 at 02:18 +0100, Kay Sievers wrote:
> On Wed, 2008-03-19 at 11:54 -0500, James Bottomley wrote:
> > On Wed, 2008-03-19 at 13:04 +0100, Kay Sievers wrote:
> > > we like to see this in 2.6.25, as "change" events for polled devices are
> > > broken at the moment.
> >
> > I'm not happy just killing the code, since when the AN infrastructure
> > gets fixed, it will work.
>
> Who is going to fix what and when? Jeff did not even reply the last two
> weeks to the simple question why he added this filter, and why events
> need to dropped if something wants to send them. :)
Oh ... who else ... I'll fix it. It looks pretty simple: we need two
separate events for the filter: polled and AN media change notifies. We
should be able to turn either of them off, so two separate flags. They
need to be unified into the single media change event at the top of the
stack before we call udev.
This will allow us to turn off the AN notifies if we get a problem,
which was the original idea.
> These events are for non-AN devices, which we still poll for media
> changes. Userspace wants the same kind of events for both types of
> devices.
>
> > How about this instead as a fix for 2.6.25?
>
> We are currently working on a the next generation of the storage part of
> the hal daemon, which needs these events. So it would be nice, if we can
> make them working now, like they worked with Kristens original patches.
If we emit the same event at the top of the stack, what more needs be
done? I take it all you want is an indication that we will be using AN
instead of polling, which you will be able to get from the sysfs file.
James
next prev parent reply other threads:[~2008-03-20 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 12:04 [PATCH] fix media change events for polled devices Kay Sievers
2008-03-19 16:54 ` James Bottomley
2008-03-20 1:18 ` Kay Sievers
2008-03-20 1:25 ` James Bottomley [this message]
2008-03-20 2:16 ` 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=1205976357.11527.63.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=david@fubar.dk \
--cc=jeff@garzik.org \
--cc=kaccardi@gmail.com \
--cc=kay.sievers@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox