Netdev List
 help / color / mirror / Atom feed
From: "Kadosh, MoriyaX" <moriyax.kadosh@intel.com>
To: "Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
	"Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>,
	Daiki Harada <daiky0325@gmail.com>,
	"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>
Cc: "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>, Kohei Enju <kohei@enjuk.jp>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1 2/2] igc: use napi_schedule_irqoff() instead of napi_schedule()
Date: Thu, 14 May 2026 10:38:04 +0300	[thread overview]
Message-ID: <f30aef93-0a6b-4012-8732-cdff915ac3fa@intel.com> (raw)
In-Reply-To: <8607e5ca-9224-4803-91ac-fc0964f79e2f@intel.com>



On 05/04/2026 11:21, Ruinskiy, Dima wrote:
> On 01/04/2026 10:53, Loktionov, Aleksandr wrote:
>>
>>
>>> -----Original Message-----
>>> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf
>>> Of Daiki Harada
>>> Sent: Tuesday, March 31, 2026 12:39 PM
>>> To: intel-wired-lan@lists.osuosl.org; netdev@vger.kernel.org; linux-
>>> kernel@vger.kernel.org
>>> Cc: 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>; Daiki Harada <daiky0325@gmail.com>; Kohei
>>> Enju <kohei@enjuk.jp>
>>> Subject: [Intel-wired-lan] [PATCH iwl-next v1 2/2] igc: use
>>> napi_schedule_irqoff() instead of napi_schedule()
>>>
>>> Replace napi_schedule() with napi_schedule_irqoff() in the interrupt
>>> handler path in igc driver Tested on Intel Corporation Ethernet
>>> Controller I226-V.
>>>
>>> Suggested-by: Kohei Enju <kohei@enjuk.jp>
>>> Signed-off-by: Daiki Harada <daiky0325@gmail.com>
>>> ---
>>>   drivers/net/ethernet/intel/igc/igc_main.c | 6 +++---
>>>   1 file changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/net/ethernet/intel/igc/igc_main.c
>>> b/drivers/net/ethernet/intel/igc/igc_main.c
>>> index 72bc5128d8b8..712605886104 100644
>>> --- a/drivers/net/ethernet/intel/igc/igc_main.c
>>> +++ b/drivers/net/ethernet/intel/igc/igc_main.c
>>> @@ -5688,7 +5688,7 @@ static irqreturn_t igc_msix_ring(int irq, void
>>> *data)
>>>       /* Write the ITR value calculated from the previous interrupt.
>>> */
>>>       igc_write_itr(q_vector);
>>>
>>> -    napi_schedule(&q_vector->napi);
>>> +    napi_schedule_irqoff(&q_vector->napi);
>>>
>>>       return IRQ_HANDLED;
>>>   }
>>> @@ -6059,7 +6059,7 @@ static irqreturn_t igc_intr_msi(int irq, void
>>> *data)
>>>       if (icr & IGC_ICR_TS)
>>>           igc_tsync_interrupt(adapter);
>>>
>>> -    napi_schedule(&q_vector->napi);
>>> +    napi_schedule_irqoff(&q_vector->napi);
>>>
>>>       return IRQ_HANDLED;
>>>   }
>>> @@ -6105,7 +6105,7 @@ static irqreturn_t igc_intr(int irq, void *data)
>>>       if (icr & IGC_ICR_TS)
>>>           igc_tsync_interrupt(adapter);
>>>
>>> -    napi_schedule(&q_vector->napi);
>>> +    napi_schedule_irqoff(&q_vector->napi);
>>>
>>>       return IRQ_HANDLED;
>>>   }
>>> -- 
>>> 2.53.0
>>
>> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
>>
> Reviewed-by: Dima Ruinskiy <dima.ruinskiy@intel.com>

Tested-By: Moriya Kadosh <moriyax.kadosh@intel.com>

      reply	other threads:[~2026-05-14  7:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 10:39 [PATCH iwl-next v1 0/2] igb/igc: use napi_schedule_irqoff() instead of napi_schedule() Daiki Harada
2026-03-31 10:39 ` [PATCH iwl-next v1 1/2] igb: " Daiki Harada
2026-04-01  7:52   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-05-12  6:16   ` Rinitha, SX
2026-03-31 10:39 ` [PATCH iwl-next v1 2/2] igc: " Daiki Harada
2026-04-01  7:53   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-05  8:21     ` Ruinskiy, Dima
2026-05-14  7:38       ` Kadosh, MoriyaX [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=f30aef93-0a6b-4012-8732-cdff915ac3fa@intel.com \
    --to=moriyax.kadosh@intel.com \
    --cc=aleksandr.loktionov@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=daiky0325@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dima.ruinskiy@intel.com \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kohei@enjuk.jp \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@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