All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Behún" <marek.behun@nic.cz>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	netdev@vger.kernel.org,
	Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: marvell 6190 NAT performance
Date: Fri, 25 Jan 2019 13:09:56 +0100	[thread overview]
Message-ID: <20190125130956.43e61268@dellmb.labs.office.nic.cz> (raw)
In-Reply-To: <ea329d29-36eb-0eec-666f-1cc12940b16f@gmail.com>

On Thu, 24 Jan 2019 13:31:24 -0800
Florian Fainelli <f.fainelli@gmail.com> wrote:

> On 1/24/19 12:26 PM, Marek Behun wrote:
> > Hello,
> > 
> > I am encountering strange performance issue when benchmarking NAT
> > performance on Armada 3720 with Marvell 88e6190 switch.
> > 
> > Download speed (from internet, via Armada 3720 NAT, via switch to
> > LAN device) is ~750mbps and the CPU running on 100% (mostly in
> > ksoftirq). Upload speed is ~250mbps.
> > 
> > When the LAN device is connected to A3720 directly (via SFP), the
> > speeds are both ~1000mbps.  
> 
> OK and that presumably uses the second Ethernet MAC on the SoC right?

SFP port uses the same Ethernet MAC as switch.
eth0 is used for wan, eth1 is either connected to a SFP cage or to a
switch chip.

> > 
> > I realize that packing/unpacking packets with Marvell header for the
> > switch takes some time, but is such a performance drop expected?  
> 
> If you run perf top/record you would be able to see that pretty
> quickly, I would not think that processing of the Marvell DSA tag
> would incur such a high penalty though since the packets are already
> hot in D$ by the time we get to mangle them for the DSA network
> devices.
> 
> How about pure (non-NAT) IP routing? How about just bridging between
> WAN and LAN?

I will try to do various benchmarks and send the results.

Marek


  reply	other threads:[~2019-01-25 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 20:26 marvell 6190 NAT performance Marek Behun
2019-01-24 21:31 ` Florian Fainelli
2019-01-25 12:09   ` Marek Behún [this message]
2019-01-29 14:27   ` Marek Behún
2019-01-29 14:56     ` Andrew Lunn

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=20190125130956.43e61268@dellmb.labs.office.nic.cz \
    --to=marek.behun@nic.cz \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.