On Wed, Jan 17, 2018 at 4:06 PM, Jesus Sanchez-Palencia
wrote:
> This series is the v2 of the Time based packet transmission RFC, which was
> originally proposed by Richard Cochran: https://lwn.net/Articles/733962/ .
Great to see you carrying on with this!
> Our main questions at this stage are
On Sun, Oct 8, 2017 at 9:06 AM, Richard Cochran
wrote:
>> +static int mv88e6xxx_ptp_enable_perout(struct mv88e6xxx_chip *chip,
>> +struct ptp_clock_request *rq, int on)
>> +{
>> + struct timespec ts;
>> + u64 ns;
>> + int pin;
>> + int err;
>> +
(apologies to davem for the repeat; I accidentally did a reply vs.
reply-all the first time)
On Thu, Oct 5, 2017 at 1:05 PM, David Miller wrote:
> From: Rodney Cummings
> Date: Thu, 5 Oct 2017 18:41:48 +
>
>> The IEEE Std 802.1Q specs for credit-based shaper require precise transmit
>> deci
On Wed, Oct 4, 2017 at 12:36 AM, Jiri Pirko wrote:
>>+static struct Qdisc_ops cbs_qdisc_ops __read_mostly = {
>>+ .next = NULL,
>>+ .id = "cbs",
>>+ .priv_size = sizeof(struct cbs_sched_data),
>>+ .enqueue= cbs_enqueue
Hi Rodney,
On Mon, Oct 2, 2017 at 1:40 PM, Rodney Cummings wrote:
> It's a shame that someone built such hardware. Speaking as a manufacturer
> of daisy-chainable products for industrial/automotive applications, I
> wouldn't use that hardware in my products. The whole point of scheduling
> is to
Hi Rodney,
Some archives seem to have threaded it, but I have CC'd the
participants I saw in the original discussion thread since they may
not otherwise notice it amongst the normal traffic.
On Fri, Sep 29, 2017 at 2:44 PM, Rodney Cummings wrote:
> Hi,
>
> I am posting my reply to this thread af
