From: "Abdul Rahim, Faizal" <faizal.abdul.rahim@linux.intel.com>
To: "Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: "intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Choong, Chwee Lin" <chwee.lin.choong@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1 6/8] igc: add preemptible queue support in taprio
Date: Tue, 29 Apr 2025 11:39:00 +0800 [thread overview]
Message-ID: <b6852273-314c-46a3-9388-3039a69b3ed8@linux.intel.com> (raw)
In-Reply-To: <SJ0PR11MB5866B4EC7D136421FCF6BBC2E5812@SJ0PR11MB5866.namprd11.prod.outlook.com>
On 28/4/2025 5:11 pm, Loktionov, Aleksandr wrote:
>
>
>> -----Original Message-----
>> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
>> Faizal Rahim
>> Sent: Monday, April 28, 2025 8:02 AM
>> To: Nguyen, Anthony L <anthony.l.nguyen@intel.com>; Kitszel, Przemyslaw
>> <przemyslaw.kitszel@intel.com>; Andrew Lunn <andrew+netdev@lunn.ch>;
>> David S . Miller <davem@davemloft.net>; Eric Dumazet
>> <edumazet@google.com>; Jakub Kicinski <kuba@kernel.org>; Paolo Abeni
>> <pabeni@redhat.com>; Vladimir Oltean <vladimir.oltean@nxp.com>
>> Cc: intel-wired-lan@lists.osuosl.org; netdev@vger.kernel.org; linux-
>> kernel@vger.kernel.org; Faizal Rahim <faizal.abdul.rahim@linux.intel.com>;
>> Choong, Chwee Lin <chwee.lin.choong@intel.com>
>> Subject: [Intel-wired-lan] [PATCH iwl-next v1 6/8] igc: add preemptible queue
>> support in taprio
>>
>> igc already supports enabling MAC Merge for FPE. This patch adds support for
>> preemptible queues in taprio.
>>
> Can you mention what "FPE" stands for (e.g., Frame Preemption) for better understanding? Everything else is fine for me.
> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
>
Will update. Thanks.
next prev parent reply other threads:[~2025-04-29 3:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 6:02 [Intel-wired-lan] [PATCH iwl-next v1 0/8] igc: harmonize queue priority and add preemptible queue support Faizal Rahim
2025-04-28 6:02 ` Faizal Rahim
2025-04-28 6:02 ` [Intel-wired-lan] [PATCH iwl-next v1 1/8] igc: move IGC_TXDCTL_QUEUE_ENABLE and IGC_TXDCTL_SWFLUSH Faizal Rahim
2025-04-28 6:02 ` Faizal Rahim
2025-04-28 7:01 ` [Intel-wired-lan] " Ruinskiy, Dima
2025-04-29 3:36 ` Abdul Rahim, Faizal
2025-04-28 6:02 ` [Intel-wired-lan] [PATCH iwl-next v1 2/8] igc: add TXDCTL prefix to related macros Faizal Rahim
2025-04-28 6:02 ` Faizal Rahim
2025-04-28 6:57 ` [Intel-wired-lan] " Ruinskiy, Dima
2025-04-29 3:37 ` Abdul Rahim, Faizal
2025-04-28 6:02 ` [Intel-wired-lan] [PATCH iwl-next v1 3/8] igc: refactor TXDCTL macros to use FIELD_PREP and GEN_MASK Faizal Rahim
2025-04-28 6:02 ` Faizal Rahim
2025-04-28 6:02 ` [Intel-wired-lan] [PATCH iwl-next v1 4/8] igc: assign highest TX queue number as highest priority in mqprio Faizal Rahim
2025-04-28 6:02 ` Faizal Rahim
2025-04-28 6:02 ` [Intel-wired-lan] [PATCH iwl-next v1 5/8] igc: add private flag to reverse TX queue priority in TSN mode Faizal Rahim
2025-04-28 6:02 ` Faizal Rahim
2025-04-28 6:02 ` [Intel-wired-lan] [PATCH iwl-next v1 6/8] igc: add preemptible queue support in taprio Faizal Rahim
2025-04-28 6:02 ` Faizal Rahim
2025-04-28 9:11 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-04-28 9:11 ` Loktionov, Aleksandr
2025-04-29 3:39 ` Abdul Rahim, Faizal [this message]
2025-04-28 6:02 ` [Intel-wired-lan] [PATCH iwl-next v1 7/8] igc: add preemptible queue support in mqprio Faizal Rahim
2025-04-28 6:02 ` Faizal Rahim
2025-04-28 6:02 ` [Intel-wired-lan] [PATCH iwl-next v1 8/8] igc: SW pad preemptible frames for correct mCRC calculation Faizal Rahim
2025-04-28 6:02 ` Faizal Rahim
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=b6852273-314c-46a3-9388-3039a69b3ed8@linux.intel.com \
--to=faizal.abdul.rahim@linux.intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=chwee.lin.choong@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=vladimir.oltean@nxp.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.