netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wei-Chun Chao <weichunc@plumgrid.com>
To: Or Gerlitz <ogerlitz@mellanox.com>
Cc: davem <davem@davemloft.net>, netdev <netdev@vger.kernel.org>,
	amirv@mellanox.com, yanb@mellanox.com,
	Alexei Starovoitov <ast@plumgrid.com>
Subject: Re: [PATCH net-next 0/2] net/mlx4: Add support for TCP/IP offloads of vxlan tunneling
Date: Wed, 18 Dec 2013 17:16:32 -0800	[thread overview]
Message-ID: <CACviX4G9vbHLWm3gu-S+SUSiSoawmQKAeXhRm9hZz1a7Hn=LiQ@mail.gmail.com> (raw)
In-Reply-To: <1387375528-2337-1-git-send-email-ogerlitz@mellanox.com>

Hi Or,
I tested this patch and with vxlan offload off I saw 14.x Gbps max and
with offload on I saw 24Gbps (16 and 32 threads got the same number
and 8 RSS rings in use).

Thanks,
Weichun

On Wed, Dec 18, 2013 at 6:05 AM, Or Gerlitz <ogerlitz@mellanox.com> wrote:
> Hi Dave,
>
> These two patches add mlx4 support for TCP/IP offloads under vxlan tunneling
>
> The patches are againt net-next commit 7ed2a0d "Merge branch 'for-davem'
> of git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc-next" plus the in-progress
> mlx4 series http://marc.info/?l=linux-netdev&m=138726378426919&w=2 -- the two
> patch series pretty much touch different areas and practically can be applied in any order.
>
> Or.
>
> Or Gerlitz (2):
>   net/mlx4_core: Add basic support for TCP/IP offloads under tunneling
>   net/mlx4_en: Add netdev support for TCP/IP offloads of vxlan tunneling
>
>  drivers/net/ethernet/mellanox/mlx4/en_netdev.c    |   95 +++++++++++++++++++++
>  drivers/net/ethernet/mellanox/mlx4/en_resources.c |    6 ++
>  drivers/net/ethernet/mellanox/mlx4/en_rx.c        |   15 +++-
>  drivers/net/ethernet/mellanox/mlx4/en_tx.c        |   14 +++-
>  drivers/net/ethernet/mellanox/mlx4/fw.c           |   19 ++++-
>  drivers/net/ethernet/mellanox/mlx4/main.c         |   14 +++
>  drivers/net/ethernet/mellanox/mlx4/mcg.c          |   14 +++-
>  drivers/net/ethernet/mellanox/mlx4/mlx4_en.h      |    3 +-
>  drivers/net/ethernet/mellanox/mlx4/port.c         |   41 +++++++++
>  include/linux/mlx4/cmd.h                          |    1 +
>  include/linux/mlx4/cq.h                           |    5 +
>  include/linux/mlx4/device.h                       |   37 ++++++++-
>  include/linux/mlx4/qp.h                           |    6 ++
>  13 files changed, 263 insertions(+), 7 deletions(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2013-12-19  1:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 14:05 [PATCH net-next 0/2] net/mlx4: Add support for TCP/IP offloads of vxlan tunneling Or Gerlitz
2013-12-18 14:05 ` [PATCH net-next 1/2] net/mlx4_core: Add basic support for TCP/IP offloads under tunneling Or Gerlitz
2013-12-18 14:05 ` [PATCH net-next 2/2] net/mlx4_en: Add netdev support for TCP/IP offloads of vxlan tunneling Or Gerlitz
2013-12-19  1:16 ` Wei-Chun Chao [this message]

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='CACviX4G9vbHLWm3gu-S+SUSiSoawmQKAeXhRm9hZz1a7Hn=LiQ@mail.gmail.com' \
    --to=weichunc@plumgrid.com \
    --cc=amirv@mellanox.com \
    --cc=ast@plumgrid.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=yanb@mellanox.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).