From: David Gibson <dgibson@redhat.com>
To: "Christian Benvenuti (benve)" <benve@cisco.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Sujith Sankar (ssujith)" <ssujith@cisco.com>,
Govindarajulu Varadarajan <govindarajulu90@gmail.com>,
"Neel Patel (neepatel)" <neepatel@cisco.com>,
Nishank Trivedi <nistrive@cisco.com>
Subject: Re: rtnetlink problems with Cisco enic and VFs
Date: Wed, 23 Apr 2014 09:24:58 +1000 [thread overview]
Message-ID: <20140423092458.d9b5ee99d389e30e87b86376@redhat.com> (raw)
In-Reply-To: <6CE81A2095B0024BBC77007BD04E553823E85BC2@xmb-aln-x02.cisco.com>
[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]
On Tue, 22 Apr 2014 19:14:04 +0000
"Christian Benvenuti (benve)" <benve@cisco.com> wrote:
> David,
>
> > -----Original Message-----
> > From: David Gibson [mailto:dgibson@redhat.com]
> > Sent: Monday, April 21, 2014 9:14 PM
> > To: netdev@vger.kernel.org
> > Cc: Christian Benvenuti (benve); Sujith Sankar (ssujith); Govindarajulu
> > Varadarajan; Neel Patel (neepatel); Nishank Trivedi
> > Subject: RFC: rtnetlink problems with Cisco enic and VFs
> >
> > I believe I've found a problem with netlink handling which can be triggered
> > on Cisco enic devices with a large number (30-40) of virtual functions. I
> > believe this is the cause of a real customer problem we've seen.
> >
> > * When requesting a list of interfaces with RTM_GETLINK, enic devices
> > (and currently, _only_ enic devices) report IFLA_VF_PORTS
> > information
>
> Is the fact that Enic is the only driver implementing ndo_get_vf_port [1]
> the root cause of the problem and the reason why this happens only with Enic?
Yes, or at least it's one of the factors.
>
> /Chris
>
> [1]
> This is what makes rtnl_port_size to account for vf_port_size*dev_num_vf(...)
> and rtnl_port_fill to add IFLA_VF_PORTS.
--
David Gibson <dgibson@redhat.com>
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-04-22 23:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 4:14 RFC: rtnetlink problems with Cisco enic and VFs David Gibson
2014-04-22 4:17 ` David Gibson
2014-04-22 18:03 ` Ben Hutchings
2014-04-22 18:12 ` David Miller
2014-04-22 23:26 ` David Gibson
2014-04-23 0:04 ` Greg Rose
2014-04-23 1:12 ` David Gibson
2014-04-23 1:16 ` David Miller
2014-04-23 2:33 ` Christian Benvenuti (benve)
2014-04-23 4:15 ` David Gibson
2014-04-23 0:59 ` David Miller
2014-04-22 19:14 ` Christian Benvenuti (benve)
2014-04-22 23:24 ` David Gibson [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=20140423092458.d9b5ee99d389e30e87b86376@redhat.com \
--to=dgibson@redhat.com \
--cc=benve@cisco.com \
--cc=govindarajulu90@gmail.com \
--cc=neepatel@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=nistrive@cisco.com \
--cc=ssujith@cisco.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).