[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180307052849.droj77rqa7epqvfe@localhost>
Date: Tue, 6 Mar 2018 21:28:49 -0800
From: Richard Cochran <richardcochran@...il.com>
To: Jesus Sanchez-Palencia <jesus.sanchez-palencia@...el.com>
Cc: netdev@...r.kernel.org, jhs@...atatu.com, xiyou.wangcong@...il.com,
jiri@...nulli.us, vinicius.gomes@...el.com,
intel-wired-lan@...ts.osuosl.org, anna-maria@...utronix.de,
henrik@...tad.us, tglx@...utronix.de, john.stultz@...aro.org,
levi.pearson@...man.com, edumazet@...gle.com, willemb@...gle.com,
mlichvar@...hat.com
Subject: Re: [RFC v3 net-next 00/18] Time based packet transmission
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 "not earlier than" or "not later
> than" a given timestamp;
> - Now on the enqueue() path, the qdisc will drop a packet if its clockid
> doesn't match the qdisc's one;
> - Sorting the packets based on their txtime is now an option for the disc.
> Effectively, this means it can be configured in 4 modes: HW offload or
> SW best-effort, sorting enabled or disabled;
While all of this makes the series and the configuration more complex,
still I like the fact that the interface offers these different modes.
Looking forward to testing this...
Thanks,
Richard
Powered by blists - more mailing lists