DPDK patches and discussions
 help / color / mirror / Atom feed
From: sujith sankar <sujithsankar2@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] ixgbe - link state change detection of port-channel members triggered from Cisco Nexus 9000
Date: Wed, 18 Oct 2017 09:57:40 +0530	[thread overview]
Message-ID: <CAMTiEwdLwBSA4rx9qVaZ8bUNwQB49k4H_ozMYjgQ=YYfUDOPhQ@mail.gmail.com> (raw)
In-Reply-To: <CAMTiEwc-2OL4ASdjc16LGDbN=FPynjOt=3405GhrV=ucTJcdng@mail.gmail.com>

Hi all,

It would be great if someone could help me with this.

Thanks,
-Sujith

On Tue, Oct 3, 2017 at 5:23 PM, sujith sankar <sujithsankar2@gmail.com> wrote:
> Hi,
>
> While testing port-channels (LACP) on ixgbe, I observed that when
> port-channel member interfaces are brought down from Cisco Nexus 9000
> switch, ixgbe PMD is not detecting it.  It was seen that LSC
> interrupts are not getting generated.  This behaviour is intermittent
> and is not seen with Linux kernel mode driver.
>
> We are using DPDK 16.04 in our code.
> Please find below the details of the NIC and switch.
>
> NIC firmware version : 0x80000887
> Switch : Cisco Nexus9000 C9372PX (observed the same on Nexus 7000 also)
> Switch firmware : 7.0(3)I1(3)
>
> This behaviour was not observed while testing with Cumulus or Netgear switches.
>
> Could the maintainers of ixgbe confirm if there are any such
> inter-operability problems between Cisco switches and Niantic cards?
> Also, is there any work-around for this?
>
> Thanks,
> -Sujith Sankar

      reply	other threads:[~2017-10-18  4:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 11:53 sujith sankar
2017-10-18  4:27 ` sujith sankar [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='CAMTiEwdLwBSA4rx9qVaZ8bUNwQB49k4H_ozMYjgQ=YYfUDOPhQ@mail.gmail.com' \
    --to=sujithsankar2@gmail.com \
    --cc=dev@dpdk.org \
    /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).