From: Patrick Mochel <mochel@osdl.org>
To: Steven Dake <sdake@mvista.com>
Cc: Greg KH <greg@kroah.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] udev enhancements to use kernel event queue
Date: Fri, 13 Jun 2003 09:41:40 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0306130925510.908-100000@cherise> (raw)
In-Reply-To: <3EE9F2E5.1050407@mvista.com>
> I suppose it is possible that devfs could be faster, however, there are
> significant amounts of policies that can never be done in devfs which
> must be done in user space. For these types of applications, it makes
> sense to provide the fastest mechanism available, even when it may only
> improve boot performance by 1 second.
Eh? Why must you completely re-engineer a solution because you see the
current one as deficient? Not only is it completely over-engineered by
enforcing your fanatical ideas about requiring a new system daemon, but
it's total pre-mature optimization.
On top of that, you don't have any accurate numbers to back up your
claims. Please perform and post the timings I suggested yesterday, and
then we'll talk.
> I understand what you mean by saying that 99.99% of users don't care
> about availability. While those particular users may spend significant
> amounts of time improving Linux, it is the remaining folks that care
> about availability that are interested in investing money into r&d to
> improve availability while also improving feature set. It is this set
> of folks, (the people that do care about availability) that this patch
> is targeted towards.
Then it is your responsibility to merge the continuing efforts and design
goals of the kernel with the requirements of your high-paying customers in
the smoothest possible way. Serving one while ignoring the other is a good
way to waste a lot of time and money.
I care about availability. But, I am not willing to integrate or support
features that come from some random person just because they claim to
improve availability, especially when a) I don't like the numbers and b)
there are no numbers to back it up.
> >As for the memory issues, if no one ever reads from the character node,
> >it will constantly fill up with events, right? Shouldn't they be
> >eventually flushed out at some point in time?
> >
> >
> This is a problem... I wasn't quite sure how to handle this. The two
> choices are to include timeouts in events (after a certain amount of
> time, events are timed out and freed) or to allow only a certain number
> of events, after which events at the front of the queue are flushed.
>
> The reality though, is that the user will be running the daemon to clear
> out the events. If they don't, then they get what they deserve :)
And this improves availability how?
-pat
next prev parent reply other threads:[~2003-06-13 16:26 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 19:10 [PATCH] udev enhancements to use kernel event queue Steven Dake
2003-06-12 21:47 ` Patrick Mochel
2003-06-13 16:31 ` Steven Dake
2003-06-13 17:06 ` Patrick Mochel
2003-06-12 21:47 ` Greg KH
2003-06-12 22:03 ` Andrew Morton
2003-06-12 22:50 ` Greg KH
2003-06-12 22:51 ` Andrew Morton
2003-06-12 23:02 ` Greg KH
2003-06-12 23:09 ` Greg KH
2003-06-12 23:14 ` Patrick Mochel
2003-06-12 23:16 ` Robert Love
2003-06-12 23:25 ` Greg KH
2003-06-13 20:01 ` Oliver Neukum
2003-06-18 22:59 ` Greg KH
2003-06-19 0:12 ` Kevin P. Fleming
2003-06-19 0:20 ` Greg KH
2003-06-19 0:42 ` Kevin P. Fleming
2003-06-19 0:51 ` Greg KH
2003-06-19 0:25 ` Andrew Morton
2003-06-19 6:27 ` Oliver Neukum
2003-06-12 23:25 ` Patrick Mochel
2003-06-12 23:29 ` Robert Love
2003-06-12 23:32 ` Greg KH
2003-06-12 23:34 ` Patrick Mochel
2003-06-12 23:40 ` Paul Mackerras
2003-06-12 23:50 ` Robert Love
2003-06-13 12:44 ` Richard B. Johnson
2003-06-13 12:54 ` Olivier Galibert
2003-06-12 23:52 ` Patrick Mochel
2003-06-13 8:41 ` Alan Cox
2003-06-13 11:00 ` Paul Mackerras
2003-06-13 11:07 ` Herbert Xu
2003-06-13 13:31 ` Alan Cox
2003-06-13 19:57 ` Joe Korty
2003-06-13 21:10 ` Alan Cox
2003-06-13 11:17 ` David Schwartz
2003-06-13 15:44 ` Davide Libenzi
2003-06-12 23:42 ` Robert Love
2003-06-12 23:45 ` Davide Libenzi
2003-06-12 23:05 ` Robert Love
2003-06-19 19:51 ` Werner Almesberger
2003-06-26 12:17 ` Tommi Virtanen
2003-06-26 14:35 ` Werner Almesberger
2003-06-13 8:40 ` Alan Cox
2003-06-13 9:14 ` Olivier Galibert
2003-06-19 20:53 ` Werner Almesberger
2003-06-13 16:05 ` Steven Dake
2003-06-13 16:32 ` Greg KH
2003-06-13 15:51 ` Steven Dake
2003-06-13 16:41 ` Patrick Mochel [this message]
2003-06-13 16:42 ` Greg KH
2003-06-13 17:17 ` Chris Friesen
2003-06-12 22:27 ` Oliver Neukum
2003-06-13 16:03 ` Steven Dake
2003-06-13 16:50 ` Patrick Mochel
2003-06-13 17:10 ` Steven Dake
2003-06-13 18:26 ` Greg KH
2003-06-13 19:02 ` Patrick Mansfield
2003-06-13 17:32 ` Oliver Neukum
2003-06-13 18:23 ` Greg KH
2003-06-13 18:24 ` Greg KH
2003-06-13 7:17 ` Christoph Hellwig
2003-06-13 18:06 ` Linus Torvalds
2003-06-19 23:32 ` Werner Almesberger
2003-06-19 23:42 ` Steven Dake
2003-06-20 0:05 ` Linus Torvalds
2003-06-20 0:10 ` Steven Dake
2003-06-20 0:43 ` Linus Torvalds
2003-06-20 2:26 ` Werner Almesberger
2003-06-20 17:03 ` Steven Dake
2003-06-20 17:18 ` Patrick Mochel
2003-06-14 6:36 John Bradford
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=Pine.LNX.4.44.0306130925510.908-100000@cherise \
--to=mochel@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sdake@mvista.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;
as well as URLs for NNTP newsgroup(s).