> Followup to: <Pine.HPP.3.96.980805205308.17170K-100000@ixion.honeywell.com>
> By author: Shawn Leas <sleas@ixion.honeywell.com>
> In newsgroup: linux.dev.kernel
> >
> > 2) Ease of system maintainence. SYSV style/looking devices tell you
> > EXACTLY where your disks are at a glance, and that is GOOD. Auto device
> > generation is good too...
>
> Auto device generation can be a security hole, and can be done in user
> space without hogging tons of kernel memory.
>
> > 3) It might help performance with some configs.
> > 4) It will NEVER hurt performance, only help it if ANYTHING.
>
> devfs eats lots of kernel memory. That WILL hurt performance.
>
That's a good reason for not doing it, if it hogs up alot of
kernel memory. I don't have a clue how it's implemented, but I wouldn't
think it would be that bad... Perhaps a clue from how SUN does it, things
in /dev only change when you boot, and it's just stored on a real filesystem,
that would take much less memory I would think.
Perhaps also have the change capability as a module for those who
wish to be able to change it on the fly, and for all others just have it
done either on request or during boot.
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html