Subject: Re: [Fwd: IPoIB] - msg#00095

Previous Message by Date: click to view message preview

[Fwd: IPoIB]

Joseph Golio wrote: To whom it may concern, I originally sent this note to Alan Cox, but he has suggested that I send it to you folks. I'm new at this process so please bare with me... So, here goes. > Alan, > > I have a question. I am working on developing a Linux driver for IP over > Infiniband (IPoIB) and > have run into an issue that I need your advice. The draft standard from > the > IETF on IPoIB > encapsulation and address resolution over Infiniband networks (see the > link > below - section 6.1.1) > defines the hardware address as being 20 bytes in length. It appears that > the "netdevice.h" file in > Linux has MAX_ADDR_LEN set to 7 (at least in my version which is SuSe 7.3 > - > kernel 2.4.4). > > http://www.ietf.org/internet-drafts/draft-ietf-ipoib-ip-over-infiniband-01.txt > > Obviously, this will not. > > What do you suggest as a good solution to this problem ? > > Thanks in advance for a quick response. > > Thanks for your time, > > Joe Golio > golio@xxxxxxxx > 651-698-9350 (ext. 111) > VIEO Inc. > > VIEO: The Adaptive Application Infrastructure Management (AAIM) Company

Next Message by Date: click to view message preview

Re: [Fwd: IPoIB]

Thomas 'Dent' Mirlacher wrote: That's what I thought. Now, I can make the change to my local systems for development and we could even give instructions to our customers to make the change to their systems also. However, how would I get this change propogated to the next release of the Linux kernel (2.5.18 plus...) ? Thanks, Joe > --snip/snip > > > > I have a question. I am working on developing a Linux driver for IP > > > over > > > Infiniband (IPoIB) and > > > have run into an issue that I need your advice. The draft standard > > > from the > > > IETF on IPoIB > > > encapsulation and address resolution over Infiniband networks (see > > > the link > > > below - section 6.1.1) > > > defines the hardware address as being 20 bytes in length. It appears > > > that > > > the "netdevice.h" file in > > > Linux has MAX_ADDR_LEN set to 7 (at least in my version which is SuSe > > > 7.3 - > > for 2.5.18 at least it's set to 8, but there is no reason to not change it to > 20 beside wasting some memory > > n time for > a) broadcast address > b) device address > int netdevice > sum(m[n]) times for the multicast list > > where n == number of network devices, m == number of MC entries per device > as i can see it. > > and this "overhead" should be really acceptable :) > > ... probably you will break some "external" stuff like freeswan, but this > shouldn't be your problem. > > tm > > -- > in some way i do, and in some way i don't.

Previous Message by Thread: click to view message preview

[Fwd: IPoIB]

Joseph Golio wrote: To whom it may concern, I originally sent this note to Alan Cox, but he has suggested that I send it to you folks. I'm new at this process so please bare with me... So, here goes. > Alan, > > I have a question. I am working on developing a Linux driver for IP over > Infiniband (IPoIB) and > have run into an issue that I need your advice. The draft standard from > the > IETF on IPoIB > encapsulation and address resolution over Infiniband networks (see the > link > below - section 6.1.1) > defines the hardware address as being 20 bytes in length. It appears that > the "netdevice.h" file in > Linux has MAX_ADDR_LEN set to 7 (at least in my version which is SuSe 7.3 > - > kernel 2.4.4). > > http://www.ietf.org/internet-drafts/draft-ietf-ipoib-ip-over-infiniband-01.txt > > Obviously, this will not. > > What do you suggest as a good solution to this problem ? > > Thanks in advance for a quick response. > > Thanks for your time, > > Joe Golio > golio@xxxxxxxx > 651-698-9350 (ext. 111) > VIEO Inc. > > VIEO: The Adaptive Application Infrastructure Management (AAIM) Company

Next Message by Thread: click to view message preview

Re: [Fwd: IPoIB]

Thomas 'Dent' Mirlacher wrote: That's what I thought. Now, I can make the change to my local systems for development and we could even give instructions to our customers to make the change to their systems also. However, how would I get this change propogated to the next release of the Linux kernel (2.5.18 plus...) ? Thanks, Joe > --snip/snip > > > > I have a question. I am working on developing a Linux driver for IP > > > over > > > Infiniband (IPoIB) and > > > have run into an issue that I need your advice. The draft standard > > > from the > > > IETF on IPoIB > > > encapsulation and address resolution over Infiniband networks (see > > > the link > > > below - section 6.1.1) > > > defines the hardware address as being 20 bytes in length. It appears > > > that > > > the "netdevice.h" file in > > > Linux has MAX_ADDR_LEN set to 7 (at least in my version which is SuSe > > > 7.3 - > > for 2.5.18 at least it's set to 8, but there is no reason to not change it to > 20 beside wasting some memory > > n time for > a) broadcast address > b) device address > int netdevice > sum(m[n]) times for the multicast list > > where n == number of network devices, m == number of MC entries per device > as i can see it. > > and this "overhead" should be really acceptable :) > > ... probably you will break some "external" stuff like freeswan, but this > shouldn't be your problem. > > tm > > -- > in some way i do, and in some way i don't.