On Wed, Jun 15, 2011 at 7:25 PM, Woodruff, Robert J <robert.j.woodr...@intel.com> wrote: > Christoph wrote, >>I surely wish this constant nightmare would go away. Could we please have >>OFED trees against each kernel version in use somewhere so that we can >>just do a git pull to get these into the respective trees? > > Other people have also asked for this, i.e., a source tree for each kernel > that OFED supports that already has the backports applied, or an install.pl > option that will generate the tree for a given kernel. Perhaps we can > try to get this support in the OFED-1.5.4 release. I will bring it up > For discussion in the OFA EWG that manages the releases.
For those of us that are not hardcore kernel developers can you explain what this change would actually do? I'm not sure i understand how having a source tree with the patches already applied is any different then taking the base kernel and applying a patch tree. But then again i probably don't understand what your talking about at all (me == admin not developer). > Long term it would also be good if these lustre patches were in the upstream > kernel, which would allow them to eventually get into the Linux distros so > that > people did not have to be applying patches and building custom kernels. I think (but could be wrong) I recall some number of years ago a skirmish between the lustre developers and the kernel maintainers over their patches, which is why they never have been added. But i think some number of the patches have been applied or lustre code changes over the years, i seem to recall in the lustre 1.6 days the patch tree was monstrous, the one i applied for 2.6.18 was pretty short only 20-30 patches or so what I'd really wish for is a completely patchless version of lustre, I'd be happy with a 10% performance hit over the compilation complexity. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
