[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140805.163637.1158175402127833659.davem@davemloft.net>
Date: Tue, 05 Aug 2014 16:36:37 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: willemb@...gle.com
Cc: netdev@...r.kernel.org, eric.dumazet@...il.com,
richardcochran@...il.com
Subject: Re: [PATCH net-next v4 0/6] net-timestamp: new tx tstamps and tcp
From: Willem de Bruijn <willemb@...gle.com>
Date: Mon, 4 Aug 2014 22:11:44 -0400
> Extend socket tx timestamping:
> - allow multiple types of software timestamps aside from send (1)
> - add software timestamp on enter packet scheduling (4)
> - add software timestamp for TCP (5)
> - add software timestamp for TCP on ACK (6)
>
> The sk_flags option space is nearly exhausted. Also move the
> many timestamp options to a new sk->sk_tstamps (2).
>
> To disambiguate data when tstamps may arrive out of order,
> optionally return a sequential ID assigned at send (3).
>
> Extend Linux tx timestamping to monitoring of latency
> incurred within the kernel stack and to protocols embedded in TCP.
> Complex kernel setups may have multiple layers of queueing, including
> multiple instances of packet scheduling, and many classes per layer.
> Many applications embed discrete payloads into TCP bytestreams for
> reliability, flow control, etcetera. Detecting application tail
> latency in such scenarios relies on identifying the exact queue
> responsible if on the host, or the network latency if otherwise.
This looks really good, thanks for taking the time to refine the
interface and how the internal sequence numbering works.
Applied to net-next.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists