linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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-next] atl1c: add 4 RX/TX queue support for Mikrotik 10/25G NIC
Date: Mon, 24 May 2021 14:24:16 -0700 (PDT)	[thread overview]
Message-ID: <20210524.142416.2165023047022388991.davem@davemloft.net> (raw)
In-Reply-To: <20210524191115.2760178-1-gatis@mikrotik.com>

From: Gatis Peisenieks <gatis@mikrotik.com>
Date: Mon, 24 May 2021 22:11:15 +0300

> More RX/TX queues on a network card help spread the CPU load among
> cores and achieve higher overall networking performance. The new
> Mikrotik 10/25G NIC supports 4 RX and 4 TX queues. TX queues are
> treated with equal priority. RX queue balancing is fixed based on
> L2/L3/L4 hash.
> 
> This adds support for 4 RX/TX queues while maintaining backwards
> compatibility with older hardware.
> 
> Simultaneous TX + RX performance on AMD Threadripper 3960X
> with Mikrotik 10/25G NIC improved from 1.6Mpps to 3.2Mpps per port.
> 
> Backwards compatiblitiy was verified with AR8151 and AR8131 based
> NICs.
> 
> Signed-off-by: Gatis Peisenieks <gatis@mikrotik.com>

This does not apply cleanly to net-next, please respin.

Thank you.

  parent reply	other threads:[~2021-05-24 21:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 19:11 [PATCH net-next] atl1c: add 4 RX/TX queue support for Mikrotik 10/25G NIC Gatis Peisenieks
2021-05-24 19:52 ` Chris Snook
2021-05-25  7:27   ` Gatis Peisenieks
2021-05-24 21:24 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-17  8:53 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=20210524.142416.2165023047022388991.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).