On 17/06/14 16:22, Justin Cormack wrote: >> What do you specifically propose with the source trees? Note that the >> kernel source tree overlaps the user source tree. I do find it rather >> annoying that we have two separate trees, but not sure how to fix it. > > I was thinking one kernel tree as it is now, and then one > kernel+userspace tree that can build both. Still two trees but you > choose the one you want depending if you are going to build userspace > or not. That should be fairly simple by adding the kernel paths to the > userspace checkout script. Select which you want with checkout or > checkoutall say.
Hmm, I guess that could work. Is there any way we could use branches to our advantage instead of separate repos, especially if we can reach the stage where the user and kernel sources use the same unmodified sources? > Currently userspace source is quite a bit smaller (whole repo) but I > can see it getting a bit bigger; the other option is just to have a > single repo with both. Since git 1.9 shallow clones work properly ie > you can clone and push from them properly, so shouldnt worry about > history getting huge - currently its the checked out tree that takes > all the space though. So maybe we should just merge them... Instead of trying to come up with the ultimate set of userspace utilities, once we get the "how to easily compile applications" thing figured out, maybe the problem will automatically solve itself. >>> 6.The IO hypercalls are an issue, I wonder if they could be made more >>> generic. I had some thoughts on this a while back, will look for them. >> >> The block I/O subsystem needs work in a number of ways, including ways >> to use alternative backends. > > Also we have repos for every network backend, rather than eg having > some type of autoconfig like approach that you can specify that you > want to build a netmap interface and a snabb one... I'm not sure there's anything wrong with having multiple repos for network backends. They are quite different after all. I have a hunch that if you're doing high-performance userspace networking, you already know which backend you want. ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
