All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>, <kuba@kernel.org>, <jiri@resnulli.us>,
	<horms@kernel.org>, <przemyslaw.kitszel@intel.com>,
	<andrew@lunn.ch>, <victor.raj@intel.com>,
	<michal.wilczynski@intel.com>, <lukasz.czapnik@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v8 0/6] ice: Support 5 layer Tx scheduler topology
Date: Thu, 28 Mar 2024 14:40:11 -0700	[thread overview]
Message-ID: <dc8d9997-c1cd-1270-0d16-81e7532eaf80@intel.com> (raw)
In-Reply-To: <20240326143042.9240-1-mateusz.polchlopek@intel.com>



On 3/26/2024 7:30 AM, Mateusz Polchlopek wrote:
> For performance reasons there is a need to have support for selectable
> Tx scheduler topology. Currently firmware supports only the default
> 9-layer and 5-layer topology. This patch series enables switch from
> default to 5-layer topology, if user decides to opt-in.

This no longer applies after Michal S' series was applied
https://lore.kernel.org/intel-wired-lan/20240325213433.829161-1-michal.swiatkowski@linux.intel.com/

Can you please rebase and resend?

Thanks,
Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Cc: andrew@lunn.ch, jiri@resnulli.us, michal.wilczynski@intel.com,
	netdev@vger.kernel.org, lukasz.czapnik@intel.com,
	victor.raj@intel.com, horms@kernel.org,
	przemyslaw.kitszel@intel.com, kuba@kernel.org
Subject: Re: [Intel-wired-lan] [PATCH net-next v8 0/6] ice: Support 5 layer Tx scheduler topology
Date: Thu, 28 Mar 2024 14:40:11 -0700	[thread overview]
Message-ID: <dc8d9997-c1cd-1270-0d16-81e7532eaf80@intel.com> (raw)
In-Reply-To: <20240326143042.9240-1-mateusz.polchlopek@intel.com>



On 3/26/2024 7:30 AM, Mateusz Polchlopek wrote:
> For performance reasons there is a need to have support for selectable
> Tx scheduler topology. Currently firmware supports only the default
> 9-layer and 5-layer topology. This patch series enables switch from
> default to 5-layer topology, if user decides to opt-in.

This no longer applies after Michal S' series was applied
https://lore.kernel.org/intel-wired-lan/20240325213433.829161-1-michal.swiatkowski@linux.intel.com/

Can you please rebase and resend?

Thanks,
Tony

  parent reply	other threads:[~2024-03-28 21:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 14:30 [Intel-wired-lan] [PATCH net-next v8 0/6] ice: Support 5 layer Tx scheduler topology Mateusz Polchlopek
2024-03-26 14:30 ` Mateusz Polchlopek
2024-03-26 14:30 ` [Intel-wired-lan] [PATCH net-next v8 1/6] devlink: extend devlink_param *set pointer Mateusz Polchlopek
2024-03-26 14:30   ` Mateusz Polchlopek
2024-03-26 14:30 ` [Intel-wired-lan] [PATCH net-next v8 2/6] ice: Support 5 layer topology Mateusz Polchlopek
2024-03-26 14:30   ` Mateusz Polchlopek
2024-03-26 14:30 ` [Intel-wired-lan] [PATCH net-next v8 3/6] ice: Adjust the VSI/Aggregator layers Mateusz Polchlopek
2024-03-26 14:30   ` Mateusz Polchlopek
2024-03-26 14:30 ` [Intel-wired-lan] [PATCH net-next v8 4/6] ice: Enable switching default Tx scheduler topology Mateusz Polchlopek
2024-03-26 14:30   ` Mateusz Polchlopek
2024-03-26 14:30 ` [Intel-wired-lan] [PATCH net-next v8 5/6] ice: Add tx_scheduling_layers devlink param Mateusz Polchlopek
2024-03-26 14:30   ` Mateusz Polchlopek
2024-03-26 14:30 ` [Intel-wired-lan] [PATCH net-next v8 6/6] ice: Document tx_scheduling_layers parameter Mateusz Polchlopek
2024-03-26 14:30   ` Mateusz Polchlopek
2024-03-28 21:40 ` Tony Nguyen [this message]
2024-03-28 21:40   ` [Intel-wired-lan] [PATCH net-next v8 0/6] ice: Support 5 layer Tx scheduler topology Tony Nguyen

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=dc8d9997-c1cd-1270-0d16-81e7532eaf80@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=andrew@lunn.ch \
    --cc=horms@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=lukasz.czapnik@intel.com \
    --cc=mateusz.polchlopek@intel.com \
    --cc=michal.wilczynski@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=victor.raj@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 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.