Igmar Palsenberg wrote:
>
> > > Timur Tabi wrote:
> > > > The real advantage comes when you're writing a driver where the design is
> > > > inherently object-oriented. I can't give an example in Linux...
> > >
> > > The VFS is inherently object-oriented. Each filesystem works by
> > > overriding a few methods stored in function table structs. The MM is
> > > well on its way to being object-oriented - check out 'struct
> > > address_space'.
> >
> > Check also vm_area_struct - that's what memory contexts consist of
> > (user memory consists of objects that correspond to areas; pagein,
> > pageout, etc. are methods of these objects; mmap() and friends
> > create/manipulate/destroy them). File mappings (both shared and
> > private) are derived classes, ditto for attached shm segment, etc.
>
> To bad I don't have time to get the basic kernel code.. Would be a good
> investment in time I guess.
>
> I assume the above struct holds pointers to the essential function
> calls, with a NULL value if the're not overridden (defaults) ?
Yes. The code is here:
http://innominate.org/~graichen/projects/lxr/ident?v=v2.3&i=file_operations
No more excuses!
--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
