From: Greg KH <greg@kroah.com>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: "'Miquel van Smoorenburg'" <miquels@cistron-office.nl>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Simple Kernel-User Event Interface (Was: RE: [ANNOUNCE] udev 0.1 release)
Date: Fri, 11 Apr 2003 22:54:17 -0700 [thread overview]
Message-ID: <20030412055417.GA1966@kroah.com> (raw)
In-Reply-To: <A46BBDB345A7D5118EC90002A5072C780BEBAB1B@orsmsx116.jf.intel.com>
On Fri, Apr 11, 2003 at 09:16:02PM -0700, Perez-Gonzalez, Inaky wrote:
>
> Okay, so what about this:
>
> I started playing with a simple event interface, that would allow:
>
> - queuing events and recalling-queued events
> - not consume (almost) memory when two bazillion events are queued
> - be accessible by different processes at the same time on
> different fds
Have you looked at relayfs? I think it might do much the same thing as
this, but through a fs interface, instead of a char device node.
> Now, each fd keeps a pointer to the queue list and only when the
> event has been read by all the open fds, it is then disposed.
I don't think you can just count the number of open fds, like your patch
does to get a count of who all read this message (fds can close and
others can open, so newer fds might not have read the message before it
is removed.)
Looks like a good start, but I'm not moving the hotplug interface over
to it :)
thanks,
greg k-h
next prev parent reply other threads:[~2003-04-12 5:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 4:16 Perez-Gonzalez, Inaky
2003-04-12 5:54 ` Greg KH [this message]
2003-04-12 9:13 ` Frank van Maarseveen
2003-04-12 8:52 Perez-Gonzalez, Inaky
2003-04-12 9:23 ` Frank van Maarseveen
2003-04-15 4:41 Greg KH
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=20030412055417.GA1966@kroah.com \
--to=greg@kroah.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron-office.nl \
/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
all inboxes | Powered by JetHome®