Re: [Jack-Devel] Noisy Signal - Fragmented Data

PrevNext  Index
DateWed, 13 Apr 2016 15:01:31 +0800
From Kenneth Fields <[hidden] at gmail dot com>
To[hidden] at chriscaudle dot org
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToChris Caudle Re: [Jack-Devel] Noisy Signal - Fragmented Data
Follow-UpChris Caudle Re: [Jack-Devel] Noisy Signal - Fragmented Data
hi,
Jacktrip uses UDP. 
We are on CERNET2 and Internet2 - good IPV6 networks.
Jacktrip in the common 8-channel case would then always
send Jumbo frames, right?

8 channels x 2 bytes (16bit)  x 128 buffer size = 2048

I wonder how we did this before without problems?
Is it the different treatment of MTU on ipv6?

Ken



> On Apr 11, 2016, at 10:50 AM, Chris Caudle <[hidden]> wrote:
> 
> On Thu, April 7, 2016 6:57 am, Kenneth Fields wrote:
>> I find that with larger data chunks (over about 1500k), the packets can be
>> fragmented 2 or 3 times or more.
> 
> Do you mean 1500k or 1500 bytes?  1500 bytes is the standard maximum
> transmission unit (MTU) for Ethernet.  Anything over 1500 bytes is
> considered jumbo frames.  Most switches can be configured to accept jumbo
> frames but would drop them by default.
> 
>> Where does the fragmenting happen, on sender side? In transit?
> 
> Your network stack should determine the MTU and only send packets that
> size or below.
> 
>> Would the machine ever have any problem "reassembling" the chunks?
> 
> That is the job of the TCP part of the network stack, so it depends on
> whether the protocol you are using uses TCP, UDP, or some other
> application level protocol.
> 
> -- 
> Chris Caudle
> 
> 
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
PrevNext  Index

1460530900.22740_0.ltw:2, <DC76F9F9-4206-4CA9-80E2-6C024F3712B8 at gmail dot com>