From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Murali Karicheri <m-karicheri2@ti.com>,
Vladimir Oltean <olteanv@gmail.com>
Cc: "netdev\@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: taprio testing - Any help?
Date: Thu, 17 Oct 2019 12:32:39 -0700 [thread overview]
Message-ID: <87bluf182w.fsf@linux.intel.com> (raw)
In-Reply-To: <c4ff605f-d556-2c68-bcfd-65082ec8f73a@ti.com>
Murali Karicheri <m-karicheri2@ti.com> writes:
>
> root@am57xx-evm:~# tc qdisc replace dev eth0 parent root handle 100 taprio \
> > num_tc 4 \
> > map 2 3 1 0 2 2 2 2 2 2 2 2 2 2 2 2 \
> > queues 1@0 1@0 1@0 1@0 \
> > base-time 1564535762845777831 \
> > sched-entry S 0xC 15000000 \
> > sched-entry S 0x2 15000000 \
> > sched-entry S 0x4 15000000 \
> > sched-entry S 0x8 15000000 \
> > txtime-delay 300000 \
> > flags 0x1 \
> > clockid CLOCK_TAI
> RTNETLINK answers: Invalid argument
>
> Anything wrong with the command syntax?
I tried this example here, and it got accepted ok. I am using the
current net-next master. The first thing that comes to mind is that
perhaps you backported some old version of some of the patches (so it's
different than what's upstream now).
Cheers,
--
Vinicius
next prev parent reply other threads:[~2019-10-17 19:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 19:35 taprio testing - Any help? Murali Karicheri
2019-10-11 20:12 ` Vinicius Costa Gomes
2019-10-11 20:56 ` Murali Karicheri
2019-10-11 21:26 ` Vinicius Costa Gomes
2019-10-13 21:10 ` Vladimir Oltean
2019-10-14 15:33 ` Murali Karicheri
2019-10-14 16:18 ` taprio testing with multiple streams Murali Karicheri
2019-10-14 23:39 ` taprio testing - Any help? Vinicius Costa Gomes
2019-10-16 17:02 ` Murali Karicheri
2019-10-16 17:14 ` Murali Karicheri
2019-10-16 17:22 ` Murali Karicheri
2019-10-16 20:32 ` Vinicius Costa Gomes
2019-10-17 13:56 ` Murali Karicheri
2019-10-17 19:32 ` Vinicius Costa Gomes [this message]
2019-10-17 21:02 ` Murali Karicheri
2019-10-17 22:26 ` Murali Karicheri
2019-10-14 23:14 ` Vinicius Costa Gomes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bluf182w.fsf@linux.intel.com \
--to=vinicius.gomes@intel.com \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).