From: Subbaraya Sundeep <sbhatta@marvell.com>
To: "Gupta, Suraj" <Suraj.Gupta2@amd.com>
Cc: Sean Anderson <sean.anderson@linux.dev>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"vkoul@kernel.org" <vkoul@kernel.org>,
"Simek, Michal" <michal.simek@amd.com>,
"Pandey, Radhey Shyam" <radhey.shyam.pandey@amd.com>,
"horms@kernel.org" <horms@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"git (AMD-Xilinx)" <git@amd.com>,
"Katakam, Harini" <harini.katakam@amd.com>
Subject: Re: [PATCH net-next] net: xilinx: axienet: Configure and report coalesce parameters in DMAengine flow
Date: Wed, 28 May 2025 13:09:33 +0000 [thread overview]
Message-ID: <aDcLDdKA2GNRIY3G@f50a6ab61f9a> (raw)
In-Reply-To: <BL3PR12MB6571ABA490895FDB8225CAEBC967A@BL3PR12MB6571.namprd12.prod.outlook.com>
On 2025-05-28 at 12:00:56, Gupta, Suraj (Suraj.Gupta2@amd.com) wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
Fix your mail settings. Cannot be internal if posting to mailing list :)
Thanks,
Sundeep
> > -----Original Message-----
> > From: Sean Anderson <sean.anderson@linux.dev>
> > Sent: Tuesday, May 27, 2025 9:47 PM
> > To: Gupta, Suraj <Suraj.Gupta2@amd.com>; andrew+netdev@lunn.ch;
> > davem@davemloft.net; edumazet@google.com; kuba@kernel.org;
> > pabeni@redhat.com; vkoul@kernel.org; Simek, Michal <michal.simek@amd.com>;
> > Pandey, Radhey Shyam <radhey.shyam.pandey@amd.com>; horms@kernel.org
> > Cc: netdev@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-
> > kernel@vger.kernel.org; git (AMD-Xilinx) <git@amd.com>; Katakam, Harini
> > <harini.katakam@amd.com>
> > Subject: Re: [PATCH net-next] net: xilinx: axienet: Configure and report coalesce
> > parameters in DMAengine flow
> >
> > Caution: This message originated from an External Source. Use proper caution
> > when opening attachments, clicking links, or responding.
> >
> >
> > On 5/25/25 06:22, Suraj Gupta wrote:
> > > Add support to configure / report interrupt coalesce count and delay
> > > via ethtool in DMAEngine flow.
> > > Netperf numbers are not good when using non-dmaengine default values,
> > > so tuned coalesce count and delay and defined separate default values
> > > in dmaengine flow.
> > >
> > > Netperf numbers and CPU utilisation change in DMAengine flow after
> > > introducing coalescing with default parameters:
> > > coalesce parameters:
> > > Transfer type Before(w/o coalescing) After(with coalescing)
> > > TCP Tx, CPU utilisation% 925, 27 941, 22
> > > TCP Rx, CPU utilisation% 607, 32 741, 36
> > > UDP Tx, CPU utilisation% 857, 31 960, 28
> > > UDP Rx, CPU utilisation% 762, 26 783, 18
> > >
> > > Above numbers are observed with 4x Cortex-a53.
> >
> > How does this affect latency? I would expect these RX settings to increase latency
> > around 5-10x. I only use these settings with DIM since it will disable coalescing
> > during periods of light load for better latency.
> >
> > (of course the way to fix this in general is RSS or some other method involving
> > multiple queues).
> >
>
> I took values before NAPI addition in legacy flow (rx_threshold: 24, rx_usec: 50) as reference. But netperf numbers were low with them, so tried tuning both and selected the pair which gives good numbers.
>
> > > Signed-off-by: Suraj Gupta <suraj.gupta2@amd.com>
> > > ---
> > > This patch depend on following AXI DMA dmengine driver changes sent to
> > > dmaengine mailing list as pre-requisit series:
> > > https://lore.kernel.org/all/20250525101617.1168991-1-suraj.gupta2@amd.
> > > com/
> > > ---
> > > drivers/net/ethernet/xilinx/xilinx_axienet.h | 6 +++
> > > .../net/ethernet/xilinx/xilinx_axienet_main.c | 53 +++++++++++++++++++
> > > 2 files changed, 59 insertions(+)
> > >
> > > diff --git a/drivers/net/ethernet/xilinx/xilinx_axienet.h
> > > b/drivers/net/ethernet/xilinx/xilinx_axienet.h
> > > index 5ff742103beb..cdf6cbb6f2fd 100644
> > > --- a/drivers/net/ethernet/xilinx/xilinx_axienet.h
> > > +++ b/drivers/net/ethernet/xilinx/xilinx_axienet.h
> > > @@ -126,6 +126,12 @@
> > > #define XAXIDMA_DFT_TX_USEC 50
> > > #define XAXIDMA_DFT_RX_USEC 16
> > >
> > > +/* Default TX/RX Threshold and delay timer values for SGDMA mode with
> > DMAEngine */
> > > +#define XAXIDMAENGINE_DFT_TX_THRESHOLD 16
> > > +#define XAXIDMAENGINE_DFT_TX_USEC 5
> > > +#define XAXIDMAENGINE_DFT_RX_THRESHOLD 24
> > > +#define XAXIDMAENGINE_DFT_RX_USEC 16
> > > +
> > > #define XAXIDMA_BD_CTRL_TXSOF_MASK 0x08000000 /* First tx packet */
> > > #define XAXIDMA_BD_CTRL_TXEOF_MASK 0x04000000 /* Last tx packet */
> > > #define XAXIDMA_BD_CTRL_ALL_MASK 0x0C000000 /* All control bits */
> > > diff --git a/drivers/net/ethernet/xilinx/xilinx_axienet_main.c
> > > b/drivers/net/ethernet/xilinx/xilinx_axienet_main.c
> > > index 1b7a653c1f4e..f9c7d90d4ecb 100644
> > > --- a/drivers/net/ethernet/xilinx/xilinx_axienet_main.c
> > > +++ b/drivers/net/ethernet/xilinx/xilinx_axienet_main.c
> > > @@ -1505,6 +1505,7 @@ static int axienet_init_dmaengine(struct
> > > net_device *ndev) {
> > > struct axienet_local *lp = netdev_priv(ndev);
> > > struct skbuf_dma_descriptor *skbuf_dma;
> > > + struct dma_slave_config tx_config, rx_config;
> > > int i, ret;
> > >
> > > lp->tx_chan = dma_request_chan(lp->dev, "tx_chan0"); @@ -1520,6
> > > +1521,22 @@ static int axienet_init_dmaengine(struct net_device *ndev)
> > > goto err_dma_release_tx;
> > > }
> > >
> > > + tx_config.coalesce_cnt = XAXIDMAENGINE_DFT_TX_THRESHOLD;
> > > + tx_config.coalesce_usecs = XAXIDMAENGINE_DFT_TX_USEC;
> > > + rx_config.coalesce_cnt = XAXIDMAENGINE_DFT_RX_THRESHOLD;
> > > + rx_config.coalesce_usecs = XAXIDMAENGINE_DFT_RX_USEC;
> >
> > I think it would be clearer to just do something like
> >
> > struct dma_slave_config tx_config = {
> > .coalesce_cnt = 16,
> > .coalesce_usecs = 5,
> > };
> >
> > since these are only used once. And this ensures that you initialize the whole struct.
> >
> > But what tree are you using? I don't see these members on net-next or dmaengine.
>
> These changes are proposed in separate series in dmaengine https://lore.kernel.org/all/20250525101617.1168991-2-suraj.gupta2@amd.com/ and I described it here below my SOB.
>
> >
> > > + ret = dmaengine_slave_config(lp->tx_chan, &tx_config);
> > > + if (ret) {
> > > + dev_err(lp->dev, "Failed to configure Tx coalesce parameters\n");
> > > + goto err_dma_release_tx;
> > > + }
> > > + ret = dmaengine_slave_config(lp->rx_chan, &rx_config);
> > > + if (ret) {
> > > + dev_err(lp->dev, "Failed to configure Rx coalesce parameters\n");
> > > + goto err_dma_release_tx;
> > > + }
> > > +
> > > lp->tx_ring_tail = 0;
> > > lp->tx_ring_head = 0;
> > > lp->rx_ring_tail = 0;
> > > @@ -2170,6 +2187,19 @@ axienet_ethtools_get_coalesce(struct net_device
> > *ndev,
> > > struct axienet_local *lp = netdev_priv(ndev);
> > > u32 cr;
> > >
> > > + if (lp->use_dmaengine) {
> > > + struct dma_slave_caps tx_caps, rx_caps;
> > > +
> > > + dma_get_slave_caps(lp->tx_chan, &tx_caps);
> > > + dma_get_slave_caps(lp->rx_chan, &rx_caps);
> > > +
> > > + ecoalesce->tx_max_coalesced_frames = tx_caps.coalesce_cnt;
> > > + ecoalesce->tx_coalesce_usecs = tx_caps.coalesce_usecs;
> > > + ecoalesce->rx_max_coalesced_frames = rx_caps.coalesce_cnt;
> > > + ecoalesce->rx_coalesce_usecs = rx_caps.coalesce_usecs;
> > > + return 0;
> > > + }
> > > +
> > > ecoalesce->use_adaptive_rx_coalesce = lp->rx_dim_enabled;
> > >
> > > spin_lock_irq(&lp->rx_cr_lock);
> > > @@ -2233,6 +2263,29 @@ axienet_ethtools_set_coalesce(struct net_device
> > *ndev,
> > > return -EINVAL;
> > > }
> > >
> > > + if (lp->use_dmaengine) {
> > > + struct dma_slave_config tx_cfg, rx_cfg;
> > > + int ret;
> > > +
> > > + tx_cfg.coalesce_cnt = ecoalesce->tx_max_coalesced_frames;
> > > + tx_cfg.coalesce_usecs = ecoalesce->tx_coalesce_usecs;
> > > + rx_cfg.coalesce_cnt = ecoalesce->rx_max_coalesced_frames;
> > > + rx_cfg.coalesce_usecs = ecoalesce->rx_coalesce_usecs;
> > > +
> > > + ret = dmaengine_slave_config(lp->tx_chan, &tx_cfg);
> > > + if (ret) {
> > > + NL_SET_ERR_MSG(extack, "failed to set tx coalesce parameters");
> > > + return ret;
> > > + }
> > > +
> > > + ret = dmaengine_slave_config(lp->rx_chan, &rx_cfg);
> > > + if (ret) {
> > > + NL_SET_ERR_MSG(extack, "failed to set rx coalesce
> > parameters");
> > > + return ret;
> > > + }
> > > + return 0;
> > > + }
> > > +
> > > if (new_dim && !old_dim) {
> > > cr = axienet_calc_cr(lp, axienet_dim_coalesce_count_rx(lp),
> > > ecoalesce->rx_coalesce_usecs);
next prev parent reply other threads:[~2025-05-28 13:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 10:22 [PATCH net-next] net: xilinx: axienet: Configure and report coalesce parameters in DMAengine flow Suraj Gupta
2025-05-26 0:36 ` kernel test robot
2025-05-27 16:16 ` Sean Anderson
2025-05-28 12:00 ` Gupta, Suraj
2025-05-28 13:09 ` Subbaraya Sundeep [this message]
2025-05-29 16:17 ` Sean Anderson
2025-05-29 16:29 ` Andrew Lunn
2025-05-29 16:35 ` Sean Anderson
2025-05-30 10:18 ` Gupta, Suraj
2025-05-30 11:53 ` Gupta, Suraj
2025-05-30 20:44 ` Sean Anderson
2025-06-03 11:07 ` Gupta, Suraj
2025-06-09 16:22 ` Sean Anderson
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=aDcLDdKA2GNRIY3G@f50a6ab61f9a \
--to=sbhatta@marvell.com \
--cc=Suraj.Gupta2@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=git@amd.com \
--cc=harini.katakam@amd.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=sean.anderson@linux.dev \
--cc=vkoul@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).