Re: list.h , list_head and C++

[Robert Hancock]

remi.chateauneu@xxxxxxxxx wrote:
> On Feb 26, 2:26 pm, Robert Hancock <hanco...@xxxxxxx> wrote:
> > remi.chateau...@xxxxxxxxx wrote:
> > > My C++ program needs an intrusive list, possibly with RCU
> > > capabilities.The data structurelist_head, defined in /usr/include/
> > > linux/list.h , fits perfectly these needs.
> > You really shouldn't use kernel data structures in userspace.
> > The locking and other primitives they depend on are not guaranteed to work.
> The file starts with ' #ifdef KERNEL'  but what hurts me is
> duplicating code.
> Btw:
> - what are the fundamental reasons for not using C++ in the kernel ?

See the archives, this has been discussed before. Aside from some 
developers just not liking C++, the main problem area is that there are 
cases where C++ just does too much behind the programmer's back to be 
practical in a kernel, where things like stack usage are critical. Also, 
a number of C++ features like exceptions would be difficult to support.

> - what prevents the use of RCU lists in user mode ?

Some type of RCU list may be doable, but not with the same code. RCU 
needs to have a way of knowing that all old copies of a data structure 
are no longer in use. In the kernel this is done by checking if all CPUs 
have scheduled since accessing the structure, but that concept doesn't 
really exist in userspace.

--
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@xxxxxxxxxxxxx
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/