From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jan Medala <jan@semihalf.com>,
Evgeny Schemeilin <evgenys@amazon.com>,
matua@amazon.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v5 1/4] ena: Amazon ENA documentation
Date: Wed, 09 Mar 2016 13:39:24 +0100 [thread overview]
Message-ID: <5315941.bTAAD5uOdc@xps13> (raw)
In-Reply-To: <1457381110-20382-2-git-send-email-jan@semihalf.com>
Hi,
It is difficult to review a driver without any information about the
hardware. Do you have a web link to share?
2016-03-07 21:05, Jan Medala:
> +Supported features
> +------------------
> +
> +* Jumbo frames up to 9K
> +* Port Hardware Statistics
> +* IPv4/TCP/UDP checksum offload
> +* TSO offload
> +* Multiple receive and transmit queues
> +* RSS
> +* Low Latency Queue for Tx
Please, could you fill the table in overview.rst?
> + Currently Amazon ENA PMD driver depends on igb_uio user space I/O kernel module
You mean it would not work with VFIO?
next prev parent reply other threads:[~2016-03-09 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 20:05 [dpdk-dev] [PATCH v5 0/4] DPDK polling-mode driver for Amazon Elastic Network Adapters (ENA) Jan Medala
2016-03-07 20:05 ` [dpdk-dev] [PATCH v5 1/4] ena: Amazon ENA documentation Jan Medala
2016-03-09 12:39 ` Thomas Monjalon [this message]
2016-03-10 14:47 ` Hunt, David
2016-03-07 20:05 ` [dpdk-dev] [PATCH v5 2/4] ena: Amazon ENA communication laye Jan Medala
2016-03-09 12:55 ` Thomas Monjalon
2016-03-07 20:05 ` [dpdk-dev] [PATCH v5 3/4] ena: Amazon ENA communication layer for DPDK platform Jan Medala
2016-03-07 20:05 ` [dpdk-dev] [PATCH v5 4/4] ena: DPDK polling-mode driver for Amazon Elastic Network Adapters (ENA) Jan Medala
2016-03-10 15:22 ` Hunt, David
2016-03-09 11:34 ` [dpdk-dev] [PATCH v5 0/4] " Jan Mędala
2016-03-10 12:00 ` Bruce Richardson
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=5315941.bTAAD5uOdc@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=jan@semihalf.com \
--cc=matua@amazon.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).