From: David Miller <davem@davemloft.net>
To: gatis@mikrotik.com
Cc: chris.snook@gmail.com, kuba@kernel.org, hkallweit1@gmail.com,
jesse.brandeburg@intel.com, dchickles@marvell.com,
tully@mikrotik.com, eric.dumazet@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v4] atl1c: move tx cleanup processing out of interrupt
Date: Tue, 06 Apr 2021 16:44:46 -0700 (PDT) [thread overview]
Message-ID: <20210406.164446.1369320471860255483.davem@davemloft.net> (raw)
In-Reply-To: <c8327d4bb516dd4741878c64fa6485cd@mikrotik.com>
From: Gatis Peisenieks <gatis@mikrotik.com>
Date: Tue, 06 Apr 2021 17:49:32 +0300
> Tx queue cleanup happens in interrupt handler on same core as rx queue
> processing. Both can take considerable amount of processing in high
> packet-per-second scenarios.
>
> Sending big amounts of packets can stall the rx processing which is
> unfair
> and also can lead to out-of-memory condition since __dev_kfree_skb_irq
> queues the skbs for later kfree in softirq which is not allowed to
> happen
> with heavy load in interrupt handler.
>
> This puts tx cleanup in its own napi and enables threaded napi to
> allow
> the rx/tx queue processing to happen on different cores. Also as the
> first
> in-driver user of dev_set_threaded API, need to add EXPORT_SYMBOL for
> it.
>
> The ability to sustain equal amounts of tx/rx traffic increased:
> from 280Kpps to 1130Kpps on Threadripper 3960X with upcoming
> Mikrotik 10/25G NIC,
> from 520Kpps to 850Kpps on Intel i3-3320 with Mikrotik RB44Ge adapter.
>
> Signed-off-by: Gatis Peisenieks <gatis@mikrotik.com>
> ---
> changes since v3:
> - made scripts/checkpatch.pl happy (commit message line wrap +
> missing comment on spinlock)
> - moved the new intr_mask_lock to be besides the intr_mask it
> protects so they are more likely to be on same cacheline
> changes since v2:
> - addressed comments from Eric Dumazet
> - added EXPORT_SYMBOL for dev_set_threaded
>
> Sorry for reposting, noticed that scripts/checkpatch.pl was not happy.
This does not apply to 'net', did you mean 'net-next'? If so, please indicate this clearly in
the Subject line as per convention.
Thank you.
next prev parent reply other threads:[~2021-04-06 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 14:49 [PATCH net v4] atl1c: move tx cleanup processing out of interrupt Gatis Peisenieks
2021-04-06 23:44 ` David Miller [this message]
2021-04-07 16:55 ` Eric Dumazet
2021-04-08 5:21 ` Gatis Peisenieks
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=20210406.164446.1369320471860255483.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chris.snook@gmail.com \
--cc=dchickles@marvell.com \
--cc=eric.dumazet@gmail.com \
--cc=gatis@mikrotik.com \
--cc=hkallweit1@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tully@mikrotik.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;
as well as URLs for NNTP newsgroup(s).