:
:Hello all,
:
:for my diploma thesis, I've arranged to work on getting the DragonFlyBSD
:network stack[*] to run without the BGL. Now, it would be great if the
:code changes would become part of the project. So, my plan is to study
:the net code over easter vacation (it's been a long while since I last looked
:at it and I've never been a network guy in any case) and then post a
:preliminary roadmap on kernel@. At that point, everyone can give an opinion
:before any code gets written.
:
:Needless to say, I'm interested in any insight from the network guys and any
:references to past discussions (perhaps my searches have missed an important
:thread). You needn't refer me to stuff that's on the website.
:
:TIA,
:Aggelos
:
:[*] At least, most of the paths that matter.
That's awesome. There's a lot of work to do. Sephe has been
working on it from the driver side down towards the user side but
that's only part of the path. I've locked up the user side through
to the file pointer dispatches, but it gets the BGL the moment it
dips into the socket.
-Matt
Matthew Dillon
<dillon@backplane.com>| Linus Torvalds | Linux 2.6.27-rc8 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Linus Torvalds | Linux 2.6.20-rc6 |
| Mike Snitzer | Re: Distributed storage. |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Herbert Xu | Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state ch... |
