From: Andre Guedes <andre.guedes@linux.intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next-queue PATCH v3 1/2] igc: Add support for taprio offloading
Date: Tue, 18 Feb 2020 10:07:20 -0800 [thread overview]
Message-ID: <158204924056.42041.6687775774624197860@1.0.0.127.in-addr.arpa> (raw)
In-Reply-To: <20200214235203.3910513-2-vinicius.gomes@intel.com>
Quoting Vinicius Costa Gomes (2020-02-14 15:52:02)
> Adds support for translating taprio schedules into i225 cycles. This
> will allow schedules to run in the hardware, making the schedules
> enforcement more precise and saving CPU time.
>
> Right now, the only simple schedules are allowed, complex schedules are
> rejected. "simple" in this context are schedules that each HW queue is
> opened and closed only once in each cycle.
>
> Changing schedules is still not supported as well.
>
> Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Reviewed-by: Andre Guedes <andre.guedes@intel.com>
next prev parent reply other threads:[~2020-02-18 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 23:52 [Intel-wired-lan] [next-queue PATCH v3 0/2] igc: Add initial TSN qdiscs offloading Vinicius Costa Gomes
2020-02-14 23:52 ` [Intel-wired-lan] [next-queue PATCH v3 1/2] igc: Add support for taprio offloading Vinicius Costa Gomes
2020-02-18 18:07 ` Andre Guedes [this message]
2020-02-27 3:59 ` Brown, Aaron F
2020-03-30 23:29 ` Brown, Aaron F
2020-02-14 23:52 ` [Intel-wired-lan] [next-queue PATCH v3 2/2] igc: Add support for ETF offloading Vinicius Costa Gomes
2020-02-18 18:07 ` Andre Guedes
2020-02-27 3:46 ` Brown, Aaron F
2020-02-27 19:02 ` Vinicius Costa Gomes
2020-02-27 20:55 ` Brown, Aaron F
2020-03-30 23:29 ` Brown, Aaron F
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=158204924056.42041.6687775774624197860@1.0.0.127.in-addr.arpa \
--to=andre.guedes@linux.intel.com \
--cc=intel-wired-lan@osuosl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.