> -----Original Message----- > From: Andreas Dilger [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 28, 2006 12:41 PM > To: Lin Shen (lshen) > Cc: Eric Barton; [email protected] > Subject: Re: [Lustre-discuss] Running Luster on top of TIPC > > On Dec 28, 2006 12:04 -0800, Lin Shen (lshen) wrote: > > Yes, TIPC has a sockets API. Does this mean Luster only > uses sockets > > for its metadata and data transmission? > > No, it just means that the TCP socklnd would be relatively > straight forward to port to your networking, compared to a > completely different network stack. >
What other data transmission interface Luster uses? Doe this mean that our networking layer need to support more than just sockets API? Which part of the code would be modified for the porting? Thanks lin > > Another related question. Does Luster support jambo frame? If yes, > > what's the size of the frame? > > Yes, it does. Best efficiency is when packets are <= 8192 > bytes, so they fit into 2 pages on sender and receiver. That > means an MTU some bytes smaller than 8192 (for eth, IP, TCP headers). > > > > -----Original Message----- > > > From: Eric Barton [mailto:[EMAIL PROTECTED] > > > Sent: Friday, December 22, 2006 5:15 PM > > > To: Lin Shen (lshen); [email protected] > > > Subject: RE: [Lustre-discuss] Running Luster on top of TIPC > > > > > > > We use TIPC for inter-node communication in our system > instead of > > > > TCP/IP. Basically you can view TIPC as a light weight > non-routable > > > > TCP/IP. How hard would it be to make Luster to work on > top of it? > > > > > > Probably not difficult if it has a sockets API. > > Cheers, Andreas > -- > Andreas Dilger > Principal Software Engineer > Cluster File Systems, Inc. > _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
