From: Leon Romanovsky <leon@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org,
sasha.neftin@intel.com, muhammad.husaini.zulkifli@intel.com
Subject: Re: [PATCH net-next 0/8][pull request] Intel Wired LAN Driver Updates 2022-12-05 (igc)
Date: Wed, 7 Dec 2022 09:46:53 +0200 [thread overview]
Message-ID: <Y5BE7f9sSzjqiHf2@unreal> (raw)
In-Reply-To: <20221205212414.3197525-1-anthony.l.nguyen@intel.com>
On Mon, Dec 05, 2022 at 01:24:06PM -0800, Tony Nguyen wrote:
> Muhammad Husaini Zulkifli says:
>
> This patch series improves the Time-Sensitive Networking(TSN) Qbv Scheduling
> features. I225 stepping had some hardware restrictions; I226 enables us to
> further enhance the driver code and offer more Qbv capabilities.
<...>
> Muhammad Husaini Zulkifli (2):
> igc: remove I226 Qbv BaseTime restriction
> igc: Add checking for basetime less than zero
>
> Tan Tee Min (4):
> igc: allow BaseTime 0 enrollment for Qbv
> igc: recalculate Qbv end_time by considering cycle time
> igc: enable Qbv configuration for 2nd GCL
> igc: Set Qbv start_time and end_time to end_time if not being
> configured in GCL
>
> Vinicius Costa Gomes (2):
> igc: Use strict cycles for Qbv scheduling
> igc: Enhance Qbv scheduling by using first flag bit
>
> drivers/net/ethernet/intel/igc/igc.h | 3 +
> drivers/net/ethernet/intel/igc/igc_base.c | 29 +++
> drivers/net/ethernet/intel/igc/igc_base.h | 2 +
> drivers/net/ethernet/intel/igc/igc_defines.h | 3 +
> drivers/net/ethernet/intel/igc/igc_main.c | 224 ++++++++++++++++---
> drivers/net/ethernet/intel/igc/igc_tsn.c | 66 +++---
> drivers/net/ethernet/intel/igc/igc_tsn.h | 2 +-
> 7 files changed, 266 insertions(+), 63 deletions(-)
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2022-12-07 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 21:24 [PATCH net-next 0/8][pull request] Intel Wired LAN Driver Updates 2022-12-05 (igc) Tony Nguyen
2022-12-05 21:24 ` [PATCH net-next 1/8] igc: allow BaseTime 0 enrollment for Qbv Tony Nguyen
2022-12-05 21:24 ` [PATCH net-next 2/8] igc: remove I226 Qbv BaseTime restriction Tony Nguyen
2022-12-08 12:28 ` Kurt Kanzenbach
2022-12-09 1:50 ` Zulkifli, Muhammad Husaini
2022-12-05 21:24 ` [PATCH net-next 3/8] igc: Add checking for basetime less than zero Tony Nguyen
2022-12-05 21:24 ` [PATCH net-next 4/8] igc: recalculate Qbv end_time by considering cycle time Tony Nguyen
2022-12-05 21:24 ` [PATCH net-next 5/8] igc: enable Qbv configuration for 2nd GCL Tony Nguyen
2022-12-05 21:24 ` [PATCH net-next 6/8] igc: Set Qbv start_time and end_time to end_time if not being configured in GCL Tony Nguyen
2022-12-05 21:24 ` [PATCH net-next 7/8] igc: Use strict cycles for Qbv scheduling Tony Nguyen
2022-12-05 21:24 ` [PATCH net-next 8/8] igc: Enhance Qbv scheduling by using first flag bit Tony Nguyen
2022-12-07 7:46 ` Leon Romanovsky [this message]
2022-12-08 0:10 ` [PATCH net-next 0/8][pull request] Intel Wired LAN Driver Updates 2022-12-05 (igc) Jakub Kicinski
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=Y5BE7f9sSzjqiHf2@unreal \
--to=leon@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=muhammad.husaini.zulkifli@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sasha.neftin@intel.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).