From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: jigsaw <jigsaw@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] 82599 feature request: loopback and TSO
Date: Mon, 23 Sep 2013 10:42:29 +0200 [thread overview]
Message-ID: <201309231042.29116.thomas.monjalon@6wind.com> (raw)
Hello,
22/09/2013 20:01, jigsaw :
> Is there any plan for adding support for 82599 features such as:
>
> 1. Loopback operation for diagnostic purpose
> The Tx->Rx loopback operation is handy when debugging with a standalone 10G
> port.
>
> 2. TCP/UDP segmentation in Tx (TSE bit in DCMD)
> TSO implementation is already in kernel. Is it in the roadmap of DPDK?
I'll reword your question to "Is there anybody who is willing to
send patches for these features ?"
Note that a patch from Ivan Boule (6WIND) has already been integrated to
provide capabilities of the devices:
"ethdev: add support for device offload capabilities"
--
Thomas
next reply other threads:[~2013-09-23 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 8:42 Thomas Monjalon [this message]
2013-09-23 14:56 ` jigsaw
-- strict thread matches above, loose matches on Subject: below --
2013-09-22 18:01 jigsaw
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=201309231042.29116.thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=jigsaw@gmail.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).