> -----Original Message----- > From: Miika Komu [mailto:miika@xxxxxx] > Sent: Wednesday, April 18, 2007 10:34 PM > To: hipl-users@xxxxxxxxxxxxx > Subject: [hipl-users] Re: beet kernel patch summary > > On Wed, 18 Apr 2007, Henderson, Thomas R wrote: > > > Hi all, > > I was poking around your web site today looking for this > (interfamily) > > patch; can you send a pointer? I downloaded the nightly tarball but > > found one patch that was labeled BROKEN in the 2.6.19.0 directory. > > The latest working patches are located in patches/2.6.17.14 > directory. > 2.6.11+ are still work in progress. More specifically, 2.6.11 fails > to set-up BEET mode SPs properly. I am not sure about the above statement. 2.6.17.14 works but 2.6.11+ are still work in progress? I am not sure that I want patches that are pre-2.6.19. I see that 2.6.20.7 (today's version) has BEET, and so does 2.6.19+ I understand. Is there a separate patch on top of 2.6.19+ that does the interfamily piece of BEET? Where is that patch, and is it stable? More generally, I want to explore again a Linux implementation that requires no patches to run HIP, yet has kernel-space data processing. Loadable kernel modules are OK, as long as CONFIG_*=m in the typical distribution. This is to facilitate deployment; I think that asking testers to rebuild their kernel is too cumbersome. In the absence of something like BEET module, we would resort to custom iptables mangle modules. - is it true that 2.6.19+ as is requires no patches to do base/esp/mm HIP processing, if one does not want to do interfamily roaming? - will it be true that 2.6.2? (with interfamily) will be the same? That is, even if BEET is supported in the future, will there still be a need to apply some patch like policy-sleep to get it to work right? I understand that hipmod will be still experimental (a patch) for now, but that seems to be a separable piece. Thanks, Tom