netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "naamax.meir" <naamax.meir@linux.intel.com>
To: Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@intel.com>,
	intel-wired-lan@osuosl.org
Cc: vinicius.gomes@intel.com, kuba@kernel.org,
	anthony.l.nguyen@intel.com, leon@kernel.org, davem@davemloft.net,
	pabeni@redhat.com, edumazet@google.com,
	tee.min.tan@linux.intel.com, netdev@vger.kernel.org,
	sasha.neftin@intel.com
Subject: Re: [PATCH net-next v5] igc: offload queue max SDU from tc-taprio
Date: Thu, 23 Feb 2023 07:47:34 +0200	[thread overview]
Message-ID: <a87701b4-4b77-3b03-38f0-3c73f5573b8f@linux.intel.com> (raw)
In-Reply-To: <20230216011624.14022-1-muhammad.husaini.zulkifli@intel.com>

On 2/16/2023 03:16, Muhammad Husaini Zulkifli wrote:
> From: Tan Tee Min <tee.min.tan@linux.intel.com>
> 
> Add support for configuring the max SDU for each Tx queue.
> If not specified, keep the default.
> 
> Signed-off-by: Tan Tee Min <tee.min.tan@linux.intel.com>
> Signed-off-by: Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@intel.com>
> 
> ---
> V4 -> V5: Rework based on Jakub's comment.
> V3 -> V4: Rebase to the latest tree as per requested by Anthony.
> V2 -> V3: Rework based on Leon Romanovsky's comment.
> V1 -> V2: Rework based on Vinicius's comment.
> ---
> ---
>   drivers/net/ethernet/intel/igc/igc.h      |  1 +
>   drivers/net/ethernet/intel/igc/igc_hw.h   |  1 +
>   drivers/net/ethernet/intel/igc/igc_main.c | 33 ++++++++++++++++++++---
>   3 files changed, 31 insertions(+), 4 deletions(-)
Tested-by: Naama Meir <naamax.meir@linux.intel.com>

      reply	other threads:[~2023-02-23  5:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16  1:16 [PATCH net-next v5] igc: offload queue max SDU from tc-taprio Muhammad Husaini Zulkifli
2023-02-23  5:47 ` naamax.meir [this message]

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=a87701b4-4b77-3b03-38f0-3c73f5573b8f@linux.intel.com \
    --to=naamax.meir@linux.intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@osuosl.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=muhammad.husaini.zulkifli@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sasha.neftin@intel.com \
    --cc=tee.min.tan@linux.intel.com \
    --cc=vinicius.gomes@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).