mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Mike Bell <mike@mikebell.org>, linux-kernel@vger.kernel.org
Subject: Re: updating kernel to 2.6.13-rc1 from 2.6.12 + CONFIG_DEVFS_FS + empty /dev
Date: Sun, 3 Jul 2005 01:03:03 +0200	[thread overview]
Message-ID: <20050702230303.GA27261@alpha.home.local> (raw)
In-Reply-To: <20050702201356.GA32409@mikebell.org>

On Sat, Jul 02, 2005 at 01:13:58PM -0700, Mike Bell wrote:
> On Sat, Jul 02, 2005 at 12:03:49PM +0200, Willy Tarreau wrote:
> > They cost almost nothing, and in all cases, far less than the required code
> > to autodetect them.
> 
> I beg to differ on that. As ndevfs has shown, the code required to
> create a device node from kernel space is actually very minimal, when
> you utilize all the infrastructure already available to you in the
> kernel. libfs has most of what you need, the rest is easily stolen from
> ramfs. Almost undoubtebly much less than all those device nodes,
> especially when you consider the need to be able to perform chown/chmod
> on nodes (thus they can't be stored in the read-only flash image, but
> must instead be created at each boot on a kernel-generated filesystem
> like ramfs)

Well, here on my firewall, the /.preinit script is 1.7 kB and the init
binary which does everything (mkdir,mknod,chmod,chown,mount,...) is 5.6 kB.
I doubt you can enable devfs in a kernel for less than 8 kB. One /tmpfs
entry consumes about 600 bytes of RAM, which is still fairly acceptable
IMHO.

> devfs not utilizing it is perfectly explainable by the fact none of it
> was around way back when devfs was created. Back then kernel generated
> filesystems were proc, proc and proc. proc is pretty ugly too.

Regards,
Willy


      reply	other threads:[~2005-07-02 23:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 21:03 Eric Valette
2005-06-29 22:40 ` Greg KH
2005-06-30 13:12   ` eric.valette
2005-06-30 15:54     ` Greg KH
2005-06-30 20:27       ` Eric Valette
2005-07-02  5:37         ` Greg KH
2005-07-02  7:22           ` Eric Valette
2005-07-02  8:22             ` Willy Tarreau
2005-07-02  9:09               ` Eric Valette
2005-07-02 10:03                 ` Willy Tarreau
2005-07-02 20:13                   ` Mike Bell
2005-07-02 23:03                     ` Willy Tarreau [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=20050702230303.GA27261@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@mikebell.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

all inboxes | Powered by JetHome®