From: Joseph Golio <golio@vieo•com>
To: "Thomas 'Dent' Mirlacher" <dent@cosy•sbg.ac.at>
Cc: netdev@oss•sgi.com, gary klesk <gklesk@vieo•com>,
jeff young <jsy@vieo•com>
Subject: Re: [Fwd: IPoIB]
Date: Thu, 30 May 2002 11:13:45 -0500 [thread overview]
Message-ID: <3CF64FB9.A5F5CC21@vieo.com> (raw)
In-Reply-To: Pine.GSO.4.05.10205301751370.9848-100000@mausmaki.cosy.sbg.ac.at
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.
next prev parent reply other threads:[~2002-05-30 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 12:32 [Fwd: IPoIB] Joseph Golio
2002-05-30 15:56 ` Thomas 'Dent' Mirlacher
2002-05-30 16:13 ` Joseph Golio [this message]
2002-06-06 19:14 ` Joseph Golio
2002-06-06 19:32 ` Thomas 'Dent' Mirlacher
2002-06-06 19:59 ` Joseph Golio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CF64FB9.A5F5CC21@vieo.com \
--to=golio@vieo$(echo .)com \
--cc=dent@cosy$(echo .)sbg.ac.at \
--cc=gklesk@vieo$(echo .)com \
--cc=jsy@vieo$(echo .)com \
--cc=netdev@oss$(echo .)sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox