From: Mike Waychison <Michael.Waychison@Sun.COM>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Mike Waychison <Michael.Waychison@Sun.COM>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [autofs] [RFC] Towards a Modern Autofs
Date: Wed, 07 Jan 2004 18:47:02 -0500 [thread overview]
Message-ID: <3FFC9A76.4070407@sun.com> (raw)
In-Reply-To: <3FFC790A.3060206@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]
Jeff Garzik wrote:
> Mike Waychison wrote:
>
>> To put it into perspective, the I'm calling for the following major
>> changes:
>
> [...]
>
>> 2) move the loop that used to spin around and ask kernelspace if there
>> was anything to expire into the VFS as well, where it won't be killed.
>
> [...]
>
>> (1) and (2) shouldn't be hard at all to do considering David Howells
>> has done the majority of this already. (3) is needed in order to
>> manage direct mounts properly for when they are 'covered'.
>> Admittedly, (4) comes off as an ugly hack.
>>
>> Also, (2) was the only 'active' task the automount daemon was doing.
>> Everything else it did can be rewritten in the form of a usermode
>> helper that runs only when it is needed. This simplifies the
>> userspace code a lot.
>
>
> Just going by your own explanation here, #2 should not be in the kernel.
>
> If we moving daemons into the kernel just because they won't be killed,
> we'll have Oracle in-kernel before you know it. Completely spurious
> reason.
>
You wouldn't put a bdflush daemon in userspace either would you? The
loop in question is just that; (overly simplified):
while (1) {
f = ask_kernel_if_anything_looks_inactive();
if (f) {
try_to_umount(f);
continue;
} else {
sleep(x seconds);
}
}
My point is, if this is the only active action done by userspace, why
open it up to being broken?
--
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
mailto: Michael.Waychison@Sun.COM
http://www.sun.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[-- Attachment #2: Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2004-01-07 23:47 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b5GC-29h-1@gated-at.bofh.it>
[not found] ` <1b6CO-3v0-15@gated-at.bofh.it>
2004-01-07 4:21 ` [autofs] [RFC] Towards a Modern Autofs Andi Kleen
2004-01-07 17:50 ` H. Peter Anvin
2004-01-07 21:04 ` Mike Waychison
2004-01-07 21:11 ` Mike Fedyk
2004-01-07 23:40 ` Jesper Juhl
2004-01-07 21:24 ` Jeff Garzik
2004-01-07 23:47 ` Mike Waychison [this message]
2004-01-07 23:56 ` Jeff Garzik
2004-01-12 16:57 ` Mike Waychison
2004-01-13 7:39 ` Ian Kent
2004-01-08 19:32 trond.myklebust
2004-01-08 19:41 ` H. Peter Anvin
2004-01-08 20:08 ` trond.myklebust
2004-01-08 21:13 ` H. Peter Anvin
2004-01-08 22:20 ` J. Bruce Fields
2004-01-08 22:24 ` H. Peter Anvin
2004-01-09 20:37 ` Mike Waychison
2004-01-09 21:02 ` H. Peter Anvin
2004-01-09 21:52 ` Mike Waychison
2004-01-09 20:16 ` Mike Waychison
-- strict thread matches above, loose matches on Subject: below --
2004-01-06 23:34 Ogden, Aaron A.
2004-01-06 23:47 ` Tim Hockin
2004-01-06 22:28 Ogden, Aaron A.
2004-01-06 22:41 ` Mike Fedyk
2004-01-06 22:47 ` Tim Hockin
2004-01-06 22:53 ` Paul Raines
2004-01-07 23:14 ` Jim Carter
2004-01-07 23:32 ` H. Peter Anvin
2004-01-08 12:52 ` Ian Kent
2004-01-08 12:52 ` Ian Kent
2004-01-08 18:31 ` viro
2004-01-09 18:43 ` Ian Kent
2004-01-09 19:41 ` Mike Waychison
2004-01-09 19:57 ` H. Peter Anvin
2004-01-09 21:31 ` Mike Waychison
2004-01-09 21:36 ` H. Peter Anvin
2004-01-06 19:55 Mike Waychison
2004-01-06 21:01 ` [autofs] " H. Peter Anvin
2004-01-06 21:44 ` Mike Waychison
2004-01-06 21:50 ` Tim Hockin
2004-01-06 22:06 ` H. Peter Anvin
2004-01-06 22:17 ` Tim Hockin
[not found] ` <20040106221502.GA7398@hockin.org>
2004-01-06 22:20 ` H. Peter Anvin
2004-01-07 16:19 ` Mike Waychison
2004-01-07 17:55 ` H. Peter Anvin
2004-01-07 21:13 ` Mike Waychison
2004-01-07 21:14 ` Jim Carter
2004-01-07 22:55 ` Mike Waychison
2004-01-08 12:00 ` Ian Kent
2004-01-08 15:39 ` Mike Waychison
2004-01-09 18:20 ` Ian Kent
2004-01-09 20:06 ` Mike Waychison
2004-01-10 5:43 ` Ian Kent
2004-01-12 13:07 ` Mike Waychison
2004-01-12 16:01 ` raven
2004-01-12 16:26 ` Mike Waychison
2004-01-12 22:50 ` Tim Hockin
2004-01-12 23:28 ` Mike Waychison
2004-01-13 1:30 ` Ian Kent
2004-01-12 16:28 ` raven
2004-01-12 16:58 ` Mike Waychison
2004-01-13 1:54 ` Ian Kent
2004-01-13 19:01 ` Mike Waychison
2004-01-14 15:58 ` raven
2004-01-13 18:46 ` Mike Waychison
2004-01-09 20:51 ` Jim Carter
2004-01-10 5:56 ` Ian Kent
2004-01-08 17:34 ` H. Peter Anvin
2004-01-08 19:41 ` Mike Waychison
2004-01-08 23:42 ` Michael Clark
2004-01-09 20:28 ` Mike Waychison
2004-01-09 20:54 ` H. Peter Anvin
2004-01-09 21:43 ` Mike Waychison
2004-01-09 18:32 ` Ian Kent
2004-01-09 20:52 ` Mike Waychison
2004-01-10 6:05 ` Ian Kent
2004-01-08 12:29 ` Olivier Galibert
2004-01-08 13:20 ` Robin Rosenberg
2004-01-08 16:23 ` Mike Waychison
2004-01-08 12:35 ` Ian Kent
2004-01-08 13:08 ` Ian Kent
2004-01-08 18:20 ` Jim Carter
2004-01-08 21:01 ` H. Peter Anvin
2004-01-08 0:48 ` Ian Kent
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=3FFC9A76.4070407@sun.com \
--to=michael.waychison@sun.com \
--cc=hpa@zytor.com \
--cc=jgarzik@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.