From: Casey Leedom <leedom@chelsio.com>
To: Stefan Assmann <sassmann@redhat.com>
Cc: netdev <netdev@vger.kernel.org>,
e1000-devel@lists.sourceforge.net, "Duyck,
Alexander H" <alexander.h.duyck@intel.com>,
gregory.v.rose@intel.com, jeffrey.t.kirsher@intel.com,
Andy Gospodarek <gospo@redhat.com>
Subject: Re: [PATCH] igbvf: avoid name clash between PF and VF
Date: Wed, 30 Jun 2010 09:59:36 -0700 [thread overview]
Message-ID: <201006300959.37145.leedom@chelsio.com> (raw)
In-Reply-To: <4C2B0614.9040004@redhat.com>
| From: Stefan Assmann <sassmann@redhat.com>
| Date: Wednesday, June 30, 2010 01:53 am
|
| This is not a udev bug since udev doesn't create persistent rules for
| VFs as their MAC address changes every reboot.
|
| To avoid this problem we could change the kernel name for the VFs and
| thus avoid confusion between VFs and PFs.
|
| I've already discussed this with Alexander Duyck and Greg Rose, so far
| they have no objection. However this problem appears for all drivers that
| support PFs and VFs and thus the changes should be applied consistently
| to all of these drivers.
I'm not sure that this problem affects "all drivers which support PFs and VFs."
I think that you might mean "all drivers which support PFs and VFs with non-
persistent MAC addresses for the VFs." For instance, the MAC addresses
associated with the new cxgb4vf VFs are persistent so, from what I understand of
the scenario you outlined, I don't think that they would trigger the problem you
describe. Please correct me if I've missed something. Thanks.
Casey
next prev parent reply other threads:[~2010-06-30 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 8:53 [PATCH] igbvf: avoid name clash between PF and VF Stefan Assmann
2010-06-30 10:44 ` Ben Hutchings
2010-06-30 10:57 ` Stefan Assmann
2010-06-30 11:11 ` Kay Sievers
2010-06-30 13:07 ` Harald Hoyer
2010-06-30 16:59 ` Casey Leedom [this message]
2010-07-01 6:37 ` Stefan Assmann
2010-07-01 17:12 ` Casey Leedom
2010-07-02 6:37 ` Stefan Assmann
2010-07-08 13:41 ` Arnd Bergmann
2010-07-09 9:31 ` Stefan Assmann
2010-07-09 15:33 ` Rose, Gregory V
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=201006300959.37145.leedom@chelsio.com \
--to=leedom@chelsio.com \
--cc=alexander.h.duyck@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gospo@redhat.com \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.