ATM it doesn't look like we can enable 2.6.16 by default in 7.0. The reasons:
- java showstopper (epoll not implemented)
- futex/TLS for amd64 not in -current for testing
- futexes not completely right
- *at() not implemented
- the time to test a 2.6.16 default until 7.0 shrinks fast
Roman has some preliminary work regarding *at() and it looks good to
him. He wants me to test some stuff but I don't have enough time in
the next weeks because of work related stuff. Any volunteers to help
In p4 we have the futex/TLS stuff for amd64 but because of the futexes
not completely right part it is not committed to current yet. As we
already have the futex and TLS stuff for i386 on a similar level in
current, I would say we should go ahead and sync the amd64 stuff. It
is not used by default, so we don't break existing linux stuff and we
get the benefit of more people being able to have a look at it and
play with it. So what are your opinions, shall we give jkim@ the green
light to MFp4 the futex/TLS stuff?
Regarding the futexes not being completely right and the epoll stuff:
I think it needs to be done now, not in a month or two, else we don't
have enough time to let people play with this before the release of
7.0. Anyone with a little bit of time at hand out there? We need a
specification what the futexes are supposed to do (so far we didn't
find a good description, and the linux code is hard to read and
doesn't not really tell what it is _supposed_ to do) and we need
people which compare the current code we have with this specification.
Finding a regression test for futexes would also be nice.
A nice place to visit, but you can't stay here for long.
http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137