From: Stephen Hemminger <stephen@networkplumber.org>
To: Yong Wang <yongwang@vmware.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 0/4] vmxnet3 TSO and tx cksum offload
Date: Mon, 4 Jan 2016 21:22:25 -0800 [thread overview]
Message-ID: <20160104212225.1d824836@xeon-e3> (raw)
In-Reply-To: <1451960899-26881-1-git-send-email-yongwang@vmware.com>
On Mon, 4 Jan 2016 18:28:15 -0800
Yong Wang <yongwang@vmware.com> wrote:
> v2:
> * fixed some logging issues when debug option turned on
> * updated the txq_flags check in vmxnet3_dev_tx_queue_setup()
>
> This patchset adds TCP/UDP checksum offload and TSO to vmxnet3 PMD.
> One of the use cases for these features is to support STT. It also
> restores the tx data ring feature that was removed from a previous
> patch.
>
> Yong Wang (4):
> vmxnet3: restore tx data ring support
> vmxnet3: add tx l4 cksum offload
> vmxnet3: add TSO support
> vmxnet3: announce device offload capability
>
> doc/guides/rel_notes/release_2_3.rst | 11 +++
> drivers/net/vmxnet3/vmxnet3_ethdev.c | 16 +++-
> drivers/net/vmxnet3/vmxnet3_ring.h | 13 ---
> drivers/net/vmxnet3/vmxnet3_rxtx.c | 169 +++++++++++++++++++++++++++--------
> 4 files changed, 158 insertions(+), 51 deletions(-)
>
Overall, this looks good.
I hope STT would die (but unfortunately it won't).
prev parent reply other threads:[~2016-01-05 5:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 2:28 [PATCH v2 0/4] vmxnet3 TSO and tx cksum offload Yong Wang
2016-01-05 2:28 ` [PATCH v2 1/4] vmxnet3: restore tx data ring support Yong Wang
2016-01-05 5:16 ` Stephen Hemminger
2016-01-05 23:27 ` Yong Wang
2016-01-05 2:28 ` [PATCH v2 2/4] vmxnet3: add tx l4 cksum offload Yong Wang
2016-01-05 2:28 ` [PATCH v2 3/4] vmxnet3: add TSO support Yong Wang
2016-01-05 5:14 ` Stephen Hemminger
2016-01-05 23:45 ` Yong Wang
2016-01-05 5:15 ` Stephen Hemminger
2016-01-05 23:45 ` Yong Wang
2016-01-05 2:28 ` [PATCH v2 4/4] vmxnet3: announce device offload capability Yong Wang
2016-01-05 5:22 ` Stephen Hemminger [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=20160104212225.1d824836@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=yongwang@vmware.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 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.