Menu
▾
▴
Re: [Tipc-discussion] 64-bit processor node id
|
From: Kevin K. He <he...@ya...> - 2004-03-12 21:52:04
|
Hi Jon,
Thank you so much for all the detailed answers to
all my questions!
I am very interested in the idea of making node address
insignficant or updatable by applications (assuming
application can gurantee the new node id is unique
in the cluster). This will enable a very dynamic
cluster configuration. But I understand it's not easy.
I'd be happy to be in the loop :)
Kevin
--- Jon Maloy <jon...@er...> wrote:
---------------------------------
What will happen is that the two nodes will never connect
to each other, and the rest of the nodes in the cluster will be
very confused about this node, because there will be two
sources in the same plane, presenting themselves as this node,
but with different MAC addresses.
I may be a good idea to do as you suggest, after all the intention
is that node addresses should not be significant or even used by
well-designed applications. But I have to giv this a little more
thought.
/jon
Kevin Kaichuan He wrote:
It seems that we can't squeeze MAC address in the 12-bit node id. Then what will happen if two
processor use the same node id ? Will TIPC automatically detect the collision and even
automatically resolve the collision by assigning unique node id to each other ? Does this sound a
bad idea to implement if it's not there yet ? Kevin
--- "Ling, Xiaofeng" <xia...@in...> wrote:
currently nodeid is only 12bit, and a whole tipc address is 32bit, including zone,cluster, andnode
three part.Seems it is not so simple to change it to 64bit.
-----Original Message-----From: tip...@li...
[mailto:tip...@li...] On Behalf Of Kevin Kaichuan HeSent:
2004Äê3ÔÂ12ÈÕ 12:57To:
tip...@li...Subject: [Tipc-discussion] 64-bit processor node idCurrently
I see the driver.c uses a "int node" to storethe process node id. So it will be 32-bit node id
on32-bit processors.I am thinking that whether we can make it 64-bit. The reason is that 64-bit
integer is enough to store ethernet MAC address. So in order to generate a cluster-wide unique
node id the managment planes on different nodes don't need exchange any network packets because
they can simply use MAC addresses as their node ids.One motivation of using TIPC in our project is
that we can avoid the complexity of IP address managment in a stack of L2 switches. With 64-bit
node id, I guess every node in our stack can start tipc totally independent from others.Will there
be negative impact of 64-bit node id on the tipc ?Thank
you!Kevin-------------------------------------------------------This SF.Net email is sponsored by:
IBM Linux TutorialsFree Linux tutorial presented by Daniel Robbins, President and CEO of GenToo
technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click_______________________________________________TIPC-discussion
mailing list
TIP...@li...https://lists.sourceforge.net/lists/listinfo/tipc-discussion
-------------------------------------------------------This SF.Net email is sponsored by: IBM
Linux TutorialsFree Linux tutorial presented by Daniel Robbins, President and CEO ofGenToo
technologies. Learn everything from fundamentals to
systemadministration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click_______________________________________________TIPC-discussion
mailing
lis...@li...https://lists.sourceforge.net/lists/listinfo/tipc-discussion
This communication is confidential and intended solely for the addressee(s). Any unauthorized
review, use, disclosure or distribution is prohibited. If you believe this message has been sent
to you in error, please notify the sender by replying to this transmission and delete the message
without disclosing it. Thank you.
E-mail including attachments is susceptible to data corruption, interruption, unauthorized
amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are
not liable for any such corruption, interception, amendment, tampering or viruses or any
consequences thereof.
|
