DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Ruslan Nikolaev <ruslan@purestorage.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] MSI-X vector #1 seems to be stalled sometimes after	VF reset (ixgbe)
Date: Tue, 10 Jan 2017 10:39:52 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2026ABB52@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <33039425-355F-4D51-82EE-C5B792A1B4A0@purestorage.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ruslan Nikolaev
> Sent: Tuesday, January 10, 2017 2:48 AM
> To: dev@dpdk.org
> Subject: Re: [dpdk-dev] MSI-X vector #1 seems to be stalled sometimes
> after VF reset (ixgbe)
> 
> dpdk_vfreset.patch:
> 
> diff -urN dpdk-16.07/doc/guides/nics/overview.rst dpdk-16.07-
> new/doc/guides/nics/overview.rst
> --- dpdk-16.07/doc/guides/nics/overview.rst	2016-07-28
> 11:48:41.000000000 -0700
> +++ dpdk-16.07-new/doc/guides/nics/overview.rst	2016-12-15
> 17:32:27.436425563 -0800
> @@ -89,6 +89,7 @@
>     Speed capabilities
>     Link status            Y Y Y   Y Y   Y Y Y     Y   Y Y Y Y         Y Y
> Y Y   Y Y Y Y Y
>     Link status event      Y Y       Y     Y Y     Y   Y Y             Y Y
> Y Y     Y Y
> +   Link reset                               Y Y   Y     Y Y
>     Queue status event
> Y
>     Rx interrupt                     Y     Y Y Y Y Y Y Y Y Y Y Y Y Y Y
>     Queue start/stop           Y   Y   Y Y Y Y Y Y     Y Y     Y Y Y Y Y Y
> Y Y   Y Y

Hi,

Overview.rst is no longer in this format. 

Capabilities should now be added to the ini files in doc/guides/nics/features.

John

      reply	other threads:[~2017-01-10 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10  2:42 Ruslan Nikolaev
2017-01-10  2:47 ` Ruslan Nikolaev
2017-01-10  2:48 ` Ruslan Nikolaev
2017-01-10 10:39   ` Mcnamara, John [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=B27915DBBA3421428155699D51E4CFE2026ABB52@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=ruslan@purestorage.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).