On Tue, Jun 17, 2014 at 11:58 PM, Antti Kantee <[email protected]> wrote: > 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?
Yes I guess that could work, have one netbsd-cvs branch and scripts to create two branches with different sets of directories against it. That would make maintenance easier, and we could use it with current rumprun and buildrump as git submodules can point at a branch I think. All the patches in userspace source are not on parts used by kernel source. > > 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. Well at some point, yes, rumprun for netbsd should turn into a script to run build.sh with a special compiler. I have a plan to get there... It is still going to be helpful to have a cut down source (without the four or five compiler sources...) though. >>>> 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. Main issues are duplication of code and build infrastructure with all those projects, plus packaging issues - you want the package to just provide the driver, but currently it builds the whole rump kernel. I would expect a freebsd package to include the netmap driver for example as it ships with freebsd. Justin ------------------------------------------------------------------------------ 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
