[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100512160036.1f69fd23@dhcp-lab-109.englab.brq.redhat.com>
Date: Wed, 12 May 2010 16:00:36 +0200
From: Stanislaw Gruszka <sgruszka@...hat.com>
To: "Michael Chan" <mchan@...adcom.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Eric Dumazet" <eric.dumazet@...il.com>,
"Eilon Greenstein" <eilong@...adcom.com>,
"Vladislav Zolotarov" <vladz@...adcom.com>,
"Dmitry Kravkov" <dmitry@...adcom.com>,
"Breno Leitao" <leitao@...ux.vnet.ibm.com>,
"Matthew Carlson" <mcarlson@...adcom.com>
Subject: Re: [RFC PATCH] bnx2: use netif_carrier_off to prevent tx timeout
On Wed, 12 May 2010 06:31:52 -0700
"Michael Chan" <mchan@...adcom.com> wrote:
> > @@ -6346,6 +6338,8 @@ bnx2_vlan_rx_register(struct net_device
> > *dev, struct vlan_group *vlgrp)
> > if (bp->flags & BNX2_FLAG_CAN_KEEP_VLAN)
> > bnx2_fw_sync(bp,
> > BNX2_DRV_MSG_CODE_KEEP_VLAN_UPDATE, 0, 1);
> >
> > + if (bp->link_up)
> > + netif_carrier_on(bp->dev);
>
> Thanks Stanislaw, I think it is better to turn carrier on in
> bnx2_netif_start(). We can use the start_cnic parameter to
> decide if we need to call carrier_on().
IIRC in most cases we set carrier status in bnx2_init_nic()
(based on what we get from PHY) called before bnx2_netif_start().
One exception is bnx2_vlan_rx_register() function.
Thanks
Stanislaw
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists