mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.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>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Michael Dege <michael.dege@renesas.com>,
	Christian Mardmoeller <christian.mardmoeller@renesas.com>,
	Dennis Ostermann <dennis.ostermann@renesas.com>
Subject: Re: [PATCH net-next 1/2] net: renesas: rswitch: use per-port irq handlers
Date: Fri, 20 Dec 2024 13:16:30 +0100	[thread overview]
Message-ID: <b82ba8c6-b8ba-4045-bd65-b2cdc80d7df9@lunn.ch> (raw)
In-Reply-To: <21f0aa0e-9df3-4b5a-957a-dcf68399cdce@cogentembedded.com>

> There are only 3 physical ports, however the use case I'm targeting is -
> virtual ports serving virtual machines (with offloading features making
> hardware directly L2-forward or L3-route most traffic between outside world
> and VM-owned virtual port frontends). In this setup, some of 8 GWCA irqs
> will be given to VMs and thus there are definitely not enough to
> per-consumer allocation.

And you are describing your VMs in DT as well? And if you change your
VM setup, you are going to modify your DT? This all sounds wrong.

It sounds like you need to be able to configure the interrupt mappings
from user space somehow. And you probably need to be able to do it on
the fly, or at least, when the interface is down.

I don't know if it will help, but ethtool mentions:

       -l --show-channels
              Queries the specified network device for the numbers of  channels
              it has.  A channel is an IRQ and the set of queues that can trig‐
              ger that IRQ.

       -L --set-channels
              Changes the numbers of channels of the specified network device.

           rx N   Changes the number of channels with only receive queues.

           tx N   Changes the number of channels with only transmit queues.

           other N
                  Changes  the  number of channels used only for other purposes
                  e.g. link interrupts or SR-IOV co-ordination.

           combined N
                  Changes the number of multi-purpose channels.


Maybe there is something you can use here? Or extend.

	Andrew


  reply	other threads:[~2024-12-20 12:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20  4:16 [PATCH net-next 0/2] net: renesas: rswitch: update irq handling Nikita Yushchenko
2024-12-20  4:16 ` [PATCH net-next 1/2] net: renesas: rswitch: use per-port irq handlers Nikita Yushchenko
2024-12-20  7:59   ` Geert Uytterhoeven
2024-12-20  8:09     ` Nikita Yushchenko
2024-12-20  9:11       ` Yoshihiro Shimoda
2024-12-20  9:23         ` Nikita Yushchenko
2024-12-20  9:31           ` Andrew Lunn
2024-12-20  8:25   ` Michal Swiatkowski
2024-12-20  9:11     ` Nikita Yushchenko
2024-12-23  5:19       ` Michal Swiatkowski
2024-12-30 10:58       ` Michal Swiatkowski
2024-12-20  9:19   ` Andrew Lunn
2024-12-20  9:33     ` Nikita Yushchenko
2024-12-20 12:16       ` Andrew Lunn [this message]
2024-12-20 12:46         ` Nikita Yushchenko
2024-12-20  4:16 ` [PATCH net-next 2/2] net: renesas: rswitch: request ts interrupt at port open Nikita Yushchenko
2024-12-20  8:38   ` Michal Swiatkowski
2024-12-20  8:51     ` Nikita Yushchenko

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=b82ba8c6-b8ba-4045-bd65-b2cdc80d7df9@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=andrew+netdev@lunn.ch \
    --cc=christian.mardmoeller@renesas.com \
    --cc=davem@davemloft.net \
    --cc=dennis.ostermann@renesas.com \
    --cc=edumazet@google.com \
    --cc=geert+renesas@glider.be \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=michael.dege@renesas.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikita.yoush@cogentembedded.com \
    --cc=pabeni@redhat.com \
    --cc=yoshihiro.shimoda.uh@renesas.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®