mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: gene.haskett@verizon.net
Cc: alebyte@gmail.com, linux-kernel@vger.kernel.org,
	linux-os@chaos.analogic.com
Subject: Re: DEVFS_FS
Date: Thu, 11 Nov 2004 12:24:10 -0800	[thread overview]
Message-ID: <200411112024.iABKOAD04383@freya.yggdrasil.com> (raw)

On  2004-11-11 0:06:37, Gene Heskett wrote:
>On Wednesday 10 November 2004 16:03, Alexandre Costa wrote:
>>On Wed, 10 Nov 2004 15:46:06 -0500 (EST), linux-os
>>
>><linux-os@chaos.analogic.com> wrote:
>>> What is the approved substitute for DEVFS_FS that is marked
>>> obsolete?
>>
>>udev
>>http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html
>
>Humm, I'm not sure I'm entirely happy with that choice.  I have an 
>FC3RC5 install on an old P-II running at 233mhz, and the udev start 
>in the bootup is the slowest single thing to get started by an order 
>of magnitude.
>
>Can someone tell me a good reason udev wastes as much time as the post 
>does checking 383 megs of memory, which is very nearly a minute even 
>just for udev?
>
>If its to be used, its got to speed itself up, a LOT!.

Gene,

	I do not know what kind of device you are using or what kind
of inialization it really needs, but your situation _might_ be a good
example of the benefits of being able configure devices on demand with
devfs if this is a device that you do not use every time you boot
your system and that initialization process is not something that
can easily be deferred to the first device open() call.

	As you may know, in the recent releases of my devfs rewrite,
I split the demand loading for missing device files into a separate
a separate facility (tmpfs "lookup traps").  That way, even if you
do not want to run the rest of devfs, you could avoid that
initilization and perhaps some kernel memory usage from the device
driver in the sessions that never use that device.

	On the other hand, initialization on demand would make your
first access of the session to that device spend the same amount of
time that you are now spending at boot, whereas, you might instead
want to have that device driver loaded at boot time and stay in
kernel memory so that you can do the initialization in the background
if you can somehow ensure that access to the device will block until
the initialization completes if necessary.

                    __     ______________ 
Adam J. Richter        \ /
adam@yggdrasil.com      | g g d r a s i l

             reply	other threads:[~2004-11-11  4:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11 20:24 Adam J. Richter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-11 19:53 DEVFS_FS Adam J. Richter
2004-11-10 20:46 DEVFS_FS linux-os
2004-11-10 21:03 ` DEVFS_FS Alexandre Costa
2004-11-11  0:06   ` DEVFS_FS Gene Heskett
2004-11-11  0:19     ` DEVFS_FS Greg KH
2004-11-11  6:01       ` DEVFS_FS Gene Heskett

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=200411112024.iABKOAD04383@freya.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=alebyte@gmail.com \
    --cc=gene.haskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@chaos.analogic.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

all inboxes | Powered by JetHome®