From: David Miller <davem@davemloft.net>
To: dcaratti@redhat.com
Cc: saeedm@mellanox.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net/mlx5e: allow TSO on VXLAN over VLAN topologies
Date: Thu, 09 Jan 2020 10:52:37 -0800 (PST) [thread overview]
Message-ID: <20200109.105237.1514181450032103034.davem@davemloft.net> (raw)
In-Reply-To: <c1f4cc6214c28ce9a39147db9f3b66927dbae612.1578567988.git.dcaratti@redhat.com>
From: Davide Caratti <dcaratti@redhat.com>
Date: Thu, 9 Jan 2020 12:07:59 +0100
> since mlx5 hardware can segment correctly TSO packets on VXLAN over VLAN
> topologies, CPU usage can improve significantly if we enable tunnel
> offloads in dev->vlan_features, like it was done in the past with other
> NIC drivers (e.g. mlx4, be2net and ixgbe).
>
> Signed-off-by: Davide Caratti <dcaratti@redhat.com>
Saeed, I am assuming you will review and integrate this.
Thank you.
next prev parent reply other threads:[~2020-01-09 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 11:07 [PATCH net-next] net/mlx5e: allow TSO on VXLAN over VLAN topologies Davide Caratti
2020-01-09 18:52 ` David Miller [this message]
2020-01-14 20:33 ` Saeed Mahameed
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=20200109.105237.1514181450032103034.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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).