From: Paul Jackson <pj@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: hare@suse.de, linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Limit number of concurrent hotplug processes
Date: Wed, 28 Jul 2004 07:12:07 +0000 [thread overview]
Message-ID: <20040728001207.19723e25.pj@sgi.com> (raw)
In-Reply-To: <20040727022826.2c95d8ff.akpm@osdl.org>
Andrew wrote:
> We'd allocate the same amount of memory if we were sending
> messages up a socket/pipe to userspace, which is what we should always have
> done, instead of the direct-exec - it's caused tons of trouble.
This touches on a question I have, off-topic to the discussion of
the patch proposed by Hannes.
Doesn't doing a direct-exec have one powerful advantage over sending
some message or kevent to userspace by socket/pipe/d-bus, in that
sending the message requires that there is some userspace code already
running that is competent to receive the message?
Doing the usermodehelper direct-exec _both_ provides the thread context
in which to execute, _and_ the code to be executed. The alternative
seems to require long running threads, primed and ready to accept
particular events, cluttering up the system.
I will readily grant that this usermodehelper direct kernel exec thing
seems weird as all heck to me. But I predict that in a couple of weeks
lkml will be seeing a patch from me (the next version of the 'cpuset'
patch I'm working with Simon and Sylvain of Bull) using it -- because
the alternative of a long running, rarely used, user thread just for one
obscure particular event that required user code sucked worse.
Am I missing something? Are there _always_ better solutions than
usermodehelper's kernel direct-exec?
Or perhaps am I confusing what Andrew was referring to and the various
mechanisms available here in unfortunate ways?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id\x10040&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-07-28 7:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 13:52 [PATCH] Limit number of concurrent hotplug processes Hannes Reinecke
2004-07-26 1:20 ` Andrew Morton
2004-07-26 6:19 ` Christian Borntraeger
2004-07-26 10:59 ` Hannes Reinecke
2004-07-26 20:18 ` Andrew Morton
2004-07-27 7:04 ` Hannes Reinecke
2004-07-27 7:24 ` Andrew Morton
2004-07-27 7:59 ` Hannes Reinecke
2004-07-27 8:34 ` Andrew Morton
2004-07-27 9:05 ` Hannes Reinecke
2004-07-27 9:28 ` Andrew Morton
2004-07-27 12:22 ` Hannes Reinecke
2004-07-28 7:12 ` Paul Jackson [this message]
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=20040728001207.19723e25.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=hare@suse.de \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@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).