H. Peter Anvin writes:
> Followup to: <20000412162328.A2068@alcove.wittsend.com>
> By author: "Michael H. Warfield" <mhw@wittsend.com>
> In newsgroup: linux.dev.kernel
> >
> > I'm "on the fence". It makes my life simpler with things like the
> > device drivers I work on (getting them to show up in /dev - the Computone
> > Multiport drivers can create 520 separate devices when fully loaded) but
> > there are a lot of gotcha's where the fix (like taring up devices to
> > preserve permissions and symlinks at boot and halt) is just a butt-ugly
> > kludge.
>
> So instead there are 520 separate chunks of kernel memory... a
> device driver I'm hacking on right now is about 3x the size with
> devfs support than without
I find that really hard to believe. You'd have to make an awful lot of
calls to devfs functions to increase the code that much.
> (not to mention I can't find any documentation on the devfs kernel
> API, so I just gave up.)
So if you gave up, how do you know it's 3x bigger?
The API is documented in fs/devfs/base.c in a format designed to be
automatically extracted.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
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.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:20 EST