Re: [tipc-discussion] Solution to problem of losing fragmented messages

[Randy M. <rwm...@gm...>]

  Hi,

I agree with Jon's goals of zero copy and only copying when the user
does a read as I'm sure you do Allan.

Consider two other use cases:

1. Jumbo frame network with MTU of say 9600 bytes.
Many (well behaving) NICs will present MTU sized packet to TIPC as a
non-linear skb.
Currently TIPC linearizes these and that's fine until there's a
shortage of memory.

I submitted a patch some time ago to deal with the payload packets without
linearizing them. Is it worth re-basing and re-submitting this work?

2. The Kerlabs kernel patch uses TIPC to do transparent process migration from
one node to another. This is usually done when memory is scarce.
Louis discussed the need for a native api for zero copy send to handle
this situation.
(btw, they have an easily set-up demo using qemu on Ubuntu)

I know this doesn't help with the short term issues but I think we have to
keep the "right" design in mind and in the mailing list.

Back to the fire of the week,

-- 
../Randy/..