All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: "Nelson, Shannon" <shannon.nelson@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
	sowmini.varadhan@oracle.com
Subject: Re: [PATCH v3 net] i40e: Look up MAC address in Open Firmware or IDPROM
Date: Mon, 2 Nov 2015 14:57:07 -0500	[thread overview]
Message-ID: <20151102195707.GC15009@oracle.com> (raw)
In-Reply-To: <FC41C24E35F18A40888AACA1A36F3E418AFAD398@fmsmsx115.amr.corp.intel.com>

On (11/02/15 17:26), Nelson, Shannon wrote:
> > I assume you mean .1q 
> 
> Yes, this is what I had in mind.

I dont think we're quite there yet, even without vlans.

If I turn on/off tcpdump, there's something about the way that the link
is bounced that leaves the device down while tcpdump is running. Then
after I exit tcpdump, it bounces things a few more times again, packets
flow for a brief interval, and then there's silence.

Seems like there's is a workq that results in
i40e_service_task->i40e_sync_vsi_filters that periodically resets things.

Doing 'ip link set eth0 promisc on' keeps things nice and steady.

How is this all supposed to work if I change the macaddr from /sbin/ip 
using i40e_set_mac() and then jiggle the promisc (either just the flag,
or with tcpdump)? (I cant tell because I dont have an x86 machine with 
i40e handy)

To frame the question differently, where all should I be invoking
the new i40e_macaddr_init() function from? 

--Sowmini

  reply	other threads:[~2015-11-02 19:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 15:03 [Intel-wired-lan] [PATCH v3 net] i40e: Look up MAC address in Open Firmware or IDPROM Sowmini Varadhan
2015-10-30 15:03 ` Sowmini Varadhan
2015-10-30 18:06 ` [Intel-wired-lan] " Andy Shevchenko
2015-10-30 18:06   ` Andy Shevchenko
2015-10-30 18:12   ` [Intel-wired-lan] " Sowmini Varadhan
2015-10-30 18:12     ` Sowmini Varadhan
2015-10-30 18:20     ` [Intel-wired-lan] " Andy Shevchenko
2015-10-30 18:20       ` Andy Shevchenko
2015-10-30 18:28 ` [Intel-wired-lan] " Nelson, Shannon
2015-10-30 18:28   ` Nelson, Shannon
2015-10-30 18:36   ` [Intel-wired-lan] " Sowmini Varadhan
2015-10-30 18:36     ` Sowmini Varadhan
2015-10-30 18:57     ` [Intel-wired-lan] " Nelson, Shannon
2015-10-30 18:57       ` Nelson, Shannon
2015-10-30 19:24       ` [Intel-wired-lan] " Sowmini Varadhan
2015-10-30 19:24         ` Sowmini Varadhan
2015-10-30 22:03         ` [Intel-wired-lan] " Nelson, Shannon
2015-10-30 22:03           ` Nelson, Shannon
2015-10-30 23:13           ` [Intel-wired-lan] " Sowmini Varadhan
2015-10-30 23:13             ` Sowmini Varadhan
2015-11-01 16:24             ` [Intel-wired-lan] " Sowmini Varadhan
2015-11-01 16:24               ` Sowmini Varadhan
2015-11-01 21:03               ` [Intel-wired-lan] " Nelson, Shannon
2015-11-01 21:03                 ` Nelson, Shannon
2015-11-02  0:07                 ` Sowmini Varadhan
2015-11-02 17:26                   ` Nelson, Shannon
2015-11-02 19:57                     ` Sowmini Varadhan [this message]
2015-11-04 19:26                       ` Sowmini Varadhan

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=20151102195707.GC15009@oracle.com \
    --to=sowmini.varadhan@oracle.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=shannon.nelson@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 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.