From: Eric Barton <eeb@whamcloud.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] IPv6 NIDs
Date: Tue, 11 Oct 2011 14:20:44 +0100 [thread overview]
Message-ID: <06e901cc8818$95acbc60$c1063520$@com> (raw)
I'd like to canvass thoughts on how big an IPv6 compatible NID
might be. We'd like to start anticipating changing to these NIDs
so that current development at least doesn't dig us deeper into a
hole (e.g. on the nidtable entries sent over the wire in
imperative recovery). So here are some suggestions....
Current NID: 32 bit address-within LNET + 32 bit LNET number
64 bits / 8 bytes total
IPv6 compatible NID:
1. Minimum: 128 bit address-within-LNET + 32 bit LNET number.
160 bits / 20 bytes total.
2. Hedge a little by reserving an additional (say) 32 bits for
something we've not thought of yet and keeping the total a
multiple of 64 bits to simplify alignment.
192 bits / 24 bytes total.
3. Hedge a lot with a nice round number.
256 bits / 32 bytes total.
(2) gets my vote currently...
Cheers,
Eric
Eric Barton
CTO Whamcloud, Inc.
Tel: +44 (117) 330 1575
Mob: +44 (7920) 797 273
next reply other threads:[~2011-10-11 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 13:20 Eric Barton [this message]
2011-10-11 13:34 ` [Lustre-devel] IPv6 NIDs chas williams - CONTRACTOR
2011-10-11 17:26 ` Nathan Rutman
2011-10-12 6:18 ` Isaac Huang
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='06e901cc8818$95acbc60$c1063520$@com' \
--to=eeb@whamcloud.com \
--cc=lustre-devel@lists.lustre.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.