Hi,
On 03/08/2018 02:54 PM, Henrik Austad wrote:
> Just looking at the timestamp when the frames were received. They should be
> sent at regular intervals if I read udp_tai.c correctly, so the assumption
> was that the timestamp from tcpdump should give an inkling to how well it
> worked.
>
On Thu, Mar 08, 2018 at 10:06:46AM -0800, Jesus Sanchez-Palencia wrote:
> Hi,
>
>
> On 03/08/2018 06:09 AM, Henrik Austad wrote:
>
> (...)
>
> >
> > A lot of new knobs, I see the need, I would've like to have fewer, but
> > you've documented them pretty well. Perhaps we should add something
Hi,
On 03/08/2018 06:09 AM, Henrik Austad wrote:
(...)
>
> A lot of new knobs, I see the need, I would've like to have fewer, but
> you've documented them pretty well. Perhaps we should add something to
> Documentation/ at one stage?
Sure. The idea is working on that once the interfaces
On Tue, Mar 06, 2018 at 05:12:12PM -0800, Jesus Sanchez-Palencia wrote:
> This series is the v3 of the Time based packet transmission RFC, which was
> originally proposed by Richard Cochran (v1: https://lwn.net/Articles/733962/ )
> and further developed by us with the addition of the tbs qdisc
>
On Tue, Mar 06, 2018 at 05:12:12PM -0800, Jesus Sanchez-Palencia wrote:
> Design changes since v2:
> - Now on the dequeue() path, tbs only drops an expired packet if it has the
>skb->tc_drop_if_late flag set. In practical terms, this will define if
>the semantics of txtime on a system is
This series is the v3 of the Time based packet transmission RFC, which was
originally proposed by Richard Cochran (v1: https://lwn.net/Articles/733962/ )
and further developed by us with the addition of the tbs qdisc
(v2: https://lwn.net/Articles/744797/ ).
It introduces a new socket option
