"John R. Dunning" writes: > > We are working with cfs. That doesn't mean they're doing all our work for us > :-} > > Honestly, a big part of it is just plain old market sensitivity. Cfs is > paying attention to where their bread and butter is. So far, that's not > gentoo. Perhaps if sicortex is wildly successful we'll be able to change that > equation :-} > > ... > > So our approach has boiled down to > > 1. Stick close to vanilla > 2. Make mips work > 3. Do whatever we need to do to make lustre layer on top of that > > Based on what you've said, I wouldn't fool around with SLES, I'd just figure > out what close-to-vanilla kernel you want to start from (picking one you think > you can live with for a while) and do some part of what I described above. > You might have a somewhat easier time of it if you started with 2.6.18, as I > believe there's a cfs-supplied patchset for that one.
Thank you for your extensive feedback. :) I think you've done a pretty good job of showing the complications involved in putting together your own lustre kernel. It sounds gnarly. What I take away from this is the need for a vanilla kernel patchset from CFS, preferably for 2.6.18 or higher. If there is already at least the basis for a vanilla 2.6.18 patchset in the current beta, that could be the starting point for an ebuild that would be of use for a while. Its been awhile since I last tried running Lustre. Perhaps it is time I tried building a 2.6.18 lustre-ized kernel. It depends on how good the patchset provided by CFS is. I don't have the bandwidth to go through the extensive process that you did to get a working kernel. -bryan -- [email protected] mailing list
