From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Liu, Yong" <yong.liu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: update user guide about e1000em limitations
Date: Fri, 13 Nov 2015 17:26:27 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2023BBA92@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1446196988-3634-1-git-send-email-yong.liu@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Yong Liu
> Sent: Friday, October 30, 2015 9:23 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: update user guide about e1000em
> limitations
>
> Update interrupt related limitations for e1000em nic.
> It only support one interrupt source and not support auto-clear.
>
> Signed-off-by: Marvin Liu <yong.liu@intel.com>
>
> diff --git a/doc/guides/nics/e1000em.rst b/doc/guides/nics/e1000em.rst
> index fedafad..a84e8e1 100644
> --- a/doc/guides/nics/e1000em.rst
> +++ b/doc/guides/nics/e1000em.rst
> @@ -176,3 +176,7 @@ The following are known limitations:
> testpmd [options] -- --mbuf-size=<your-max-packet-size>
>
> #. Qemu e1000 does not validate the checksum of incoming packets.
> +
> +#. Qemu e1000 only support one interrupt source, so link and Rx
> interrupt should be exclusive.
> +
> +#. Qemu e1000 does not support interrupt auto-clear, application should
> disable interrupt immediately when waked up.
Hi Marvin,
Thanks for the clarification. Two minor typos:
Qemu e1000 only supports one interrupt source ...
... disable interrupt immediately when woken up.
When changes are made:
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2015-11-13 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 9:23 Yong Liu
2015-11-13 17:26 ` Mcnamara, John [this message]
2015-12-13 23:07 ` Thomas Monjalon
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=B27915DBBA3421428155699D51E4CFE2023BBA92@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=yong.liu@intel.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).