Re: OpenSSI status question

Roger | John,
  I could use some assistance with the following.
Linux-2.6.18, possibly before but not so far back as 2.6.10, struct sk_buff
lost the 'list' member.
Unfortunately cluster/ics/ics_tcp/ics_llsvr.c makes use of the 'list'
member.
Could one of you look into fixing cluster/ics/ics_tcp/ics_llsvr.c so it no
longer has a dependency on the list member?
>From a quick scan of other 2.6.18 drivers, the sk_buff 'list' list_head was
moved to driver local storage. The ICS channel block might be a place to
consider moving the sk_buff list head to?
This work could be prototyped and validated using R1.9.2/3 and then merged
with 2.6.18?

What do you think?  

cluster/ics/ics_tcp/ics_llsvr.c: In function '__icssvr_llenqueue':
cluster/ics/ics_tcp/ics_llsvr.c:229: error: 'struct sk_buff' has no member
named 'list'
cluster/ics/ics_tcp/ics_llsvr.c:231: error: 'struct sk_buff' has no member
named 'list'
cluster/ics/ics_tcp/ics_llsvr.c: In function 'icssvr_lldequeue':
cluster/ics/ics_tcp/ics_llsvr.c:358: error: 'struct sk_buff' has no member
named 'list'
cluster/ics/ics_tcp/ics_llsvr.c:360: error: 'struct sk_buff' has no member
named 'list'

include/linux/skbuff.h
struct sk_buff {
        /* These two members must be first. */
        struct sk_buff          *next;
        struct sk_buff          *prev;
// CONFIG_SSI & SSI_XXX - tamp addition until rewrite of icssvr/cli rtns.
        struct sk_buff_head     *list;

John,
  I strongly believe the x86_64 (aka x64) work is very important for
OpenSSI. Please make it a priority for R1.9.3.

W.r.t the 2.6.18 port, the code merge is complete, working on a clean
compile using CentOS-5 gcc 4.1.1.
R1.9.2 IB based kernel build contains 4988 .o files, so far 1367 .o files
build for 2.6.18. Not a great metric although a stake in the ground.

Stan. 

> -----Original Message-----
> From: Roger Tsang [mailto:[email protected]] 
> Sent: Thursday, October 11, 2007 3:46 AM
> To: Stan
> Cc: ssic-linux-devel; John Hughes
> Subject: Re: [SSI-devel] OpenSSI status question
> 
> I would have to agree that porting to CentOS has priority 
> over 2.6.16.y.
> 
> John - you already received the code for x86_64?
> 
> Roger
> 
> On 9/22/07, Stan <[email protected]> wrote:
> >
> >
> > > -----Original Message-----
> > > From: [email protected]
> > > [mailto:[email protected]] On
> > > Behalf Of James P. Kinney III
> > > Sent: Friday, September 21, 2007 9:03 AM
> > > To: Watson, Brian J. (HP Labs)
> > > Cc: John Hughes; ssic-linux-devel; Walker, Bruce J (HP-Labs)
> > > Subject: Re: [SSI-devel] OpenSSI status question
> > >
> > > It is back up and available now. Thanks for looking into this.
> > > John, thanks for the rsync link.
> > >
> > > Now to look at x86_64, kernel 2.6.18 and CentOS 5 (and 
> forget about
> > > sleeping) ....
> > >
> >
> > Hello James,
> >   The CenOS 5 port is moving along at the speed of a single 
> person; more
> > heads/hands would certainly help. Current status:
> >         merged openSSI code into 2.6.18 code base (base .18 
> chosen for
> > Fedora Core 6 drop?).
> >         Diffs between 2.6.18 & CentOS(2.6.18.8) manageable 
> as heavy lifting
> > done for 2.6.18.
> >         working towards a clean compile - exposing blanks 
> to fill in.
> > TBD:
> >         Debug under Fedora Core 3 (R1.9.2/3) system - 
> delays some of the
> > user-land porting?
> >         merge 2.6.18.8 diffs for CentOS 5.
> >         Port openSSI user-level code/mods into CentOS 5 env.
> >         Test, test & more testing.
> >
> > John Hughes has done the x86_64 heavy lifting in the almost 
> cooked openSSI
> > R1.9.3.
> >
> > Where can you assist?
> >
> > Stan.
> >
> >
> > 
> --------------------------------------------------------------
> -----------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > ssic-linux-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel
> >
> 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/