mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Brian Vazquez <brianvv@google.com>
Cc: Brian Vazquez <brianvv.kernel@gmail.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	intel-wired-lan@lists.osuosl.org,
	David Decotigny <decot@google.com>, Li Li <boolli@google.com>,
	Anjali Singhai <anjali.singhai@intel.com>,
	Sridhar Samudrala <sridhar.samudrala@intel.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	emil.s.tantilov@intel.com, Brett Creeley <brett.creeley@amd.com>,
	Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Subject: Re: [iwl-net PATCH v2] idpf: change IRQ naming to match netdev and ethtool queue numbering
Date: Mon, 26 Jan 2026 18:53:36 +0100	[thread overview]
Message-ID: <b18b4b38-b3e7-485f-91f8-e3a74ff90572@lunn.ch> (raw)
In-Reply-To: <CAMzD94Qt9-5G-8MHcmHLgYEyjRUoPB+SruzZXafxSTkNV8criA@mail.gmail.com>

On Mon, Jan 26, 2026 at 12:40:15PM -0500, Brian Vazquez wrote:
> On Mon, Jan 26, 2026 at 11:24 AM Andrew Lunn <andrew@lunn.ch> wrote:
> >
> > On Mon, Jan 26, 2026 at 02:46:24PM +0000, Brian Vazquez wrote:
> > > The code uses the vidx for the IRQ name but that doesn't match ethtool
> > > reporting or netdev naming, this makes it hard to tune the device and
> > > associate queues with IRQs. Sequentially requesting irqs starting from
> > > '0' makes the output consistent.
> > >
> > > Before:
> > >
> > > ethtool -L eth1 tx 1 combined 3
> > >
> > > grep . /proc/irq/*/*idpf*/../smp_affinity_list
> > > /proc/irq/67/idpf-Mailbox-0/../smp_affinity_list:0-55,112-167
> > > /proc/irq/68/idpf-eth1-TxRx-1/../smp_affinity_list:0
> > > /proc/irq/70/idpf-eth1-TxRx-3/../smp_affinity_list:1
> > > /proc/irq/71/idpf-eth1-TxRx-4/../smp_affinity_list:2
> > > /proc/irq/72/idpf-eth1-Tx-5/../smp_affinity_list:3
> > >
> > > ethtool -S eth1 | grep -v ': 0'
> > > NIC statistics:
> > >      tx_q-0_pkts: 1002
> > >      tx_q-1_pkts: 2679
> > >      tx_q-2_pkts: 1113
> > >      tx_q-3_pkts: 1192 <----- tx_q-3 vs idpf-eth1-Tx-5
> > >      rx_q-0_pkts: 1143
> > >      rx_q-1_pkts: 3172
> > >      rx_q-2_pkts: 1074
> > >
> > > After:
> > >
> > > ethtool -L eth1 tx 1 combined 3
> > >
> > > grep . /proc/irq/*/*idpf*/../smp_affinity_list
> > >
> > > /proc/irq/67/idpf-Mailbox-0/../smp_affinity_list:0-55,112-167
> > > /proc/irq/68/idpf-eth1-TxRx-0/../smp_affinity_list:0
> > > /proc/irq/70/idpf-eth1-TxRx-1/../smp_affinity_list:1
> > > /proc/irq/71/idpf-eth1-TxRx-2/../smp_affinity_list:2
> > > /proc/irq/72/idpf-eth1-Tx-3/../smp_affinity_list:3
> > >
> > > ethtool -S eth1 | grep -v ': 0'
> > > NIC statistics:
> > >      tx_q-0_pkts: 118
> > >      tx_q-1_pkts: 134
> > >      tx_q-2_pkts: 228
> > >      tx_q-3_pkts: 138 <--- tx_q-3 matches idpf-eth1-Tx-3
> > >      rx_q-0_pkts: 111
> > >      rx_q-1_pkts: 366
> > >      rx_q-2_pkts: 120
> >
> > Are there any ABI issues here?
> 
> The patch doesn't change the format, it just fixes the numbering in
> the name to make it consistent with other reporting tools. It
> shouldn't break any library.

But is the numbering part of the ABI?

Making a comment about ABI in the commit message makes it clear it is
something you have considered, and you have decided it is not an
issue. If there is no such comment, reviewers probably should ask.

       Andrew

  reply	other threads:[~2026-01-26 17:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 14:46 Brian Vazquez
2026-01-26 16:24 ` Andrew Lunn
2026-01-26 17:40   ` Brian Vazquez
2026-01-26 17:53     ` Andrew Lunn [this message]
2026-01-26 20:46       ` [Intel-wired-lan] " Jacob Keller
2026-01-26 20:51         ` Eric Dumazet
2026-01-26 21:12           ` Andrew Lunn
2026-01-26 21:55             ` Brian Vazquez
2026-01-26 17:28 ` Paul Menzel

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=b18b4b38-b3e7-485f-91f8-e3a74ff90572@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=aleksandr.loktionov@intel.com \
    --cc=anjali.singhai@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=boolli@google.com \
    --cc=brett.creeley@amd.com \
    --cc=brianvv.kernel@gmail.com \
    --cc=brianvv@google.com \
    --cc=davem@davemloft.net \
    --cc=decot@google.com \
    --cc=edumazet@google.com \
    --cc=emil.s.tantilov@intel.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=sridhar.samudrala@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

all inboxes | Powered by JetHome®