All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "Cureington, Tony" <tony.cureington@hp.com>,
	Pascal Brisset <pascal.brisset-ml@wanadoo.fr>,
	bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: [Bonding-devel] Re: Bonding driver unreliable under high CPUload
Date: Tue, 17 Sep 2002 13:30:14 -0700	[thread overview]
Message-ID: <3D8790D6.68927887@digeo.com> (raw)
In-Reply-To: 3D878C56.2070400@mandrakesoft.com

(bonding-devel didn't like the size of the attachment.
 It's at http://www.zip.com.au/~akpm/3c59x.c-netif)

Jeff Garzik wrote:
> 
> Andrew Morton wrote:
> > Jeff Garzik wrote:
> >
> >>...
> >>Also, a further question:  do you have access to the slave struct
> >>net_device?  If so, just test netif_carrier_ok(slave_dev) and avoid all
> >>that ioctl calling if it returns non-zero.
> >
> >
> > Make that "avoid all that ioctl calling from interrupt context", which
> > is a bug.  Of the box-killing variety ;)
> 
> Indeed.  /me looks at the bond_check_dev_link callers more closely and
> shudders.
> 
> That wants fixing...
> 
> Note that netif_carrier_ok() can indeed be checked in interrupt context.
>   And if someone wants to send me patches converting more drivers to use
> netif_carrier_{on,off}, I would be very happy :)

That would be best.

I'm so slack.  I received the below two years ago; Nelson has
added netif_carrier_foo support to 3c59x.c.  As Jeff says: patches
solicited.

-------- Original Message --------
Subject: Re: netlink
Date: Wed, 14 Jun 2000 11:19:33 +0800 (SST)
From: Nelson <tanginhw@comp.nus.edu.sg>
To: Andrew Morton <andrewm@uow.edu.au>
References: <394610FF.4052CEAA@uow.edu.au>

hi Andrew,

The modified 3c59x.c is attached.

for your easy reference, these lines in the attached driver 
was modified:

69-72:		notes on what are added
121-123:	defined the time to expiry of the vertex_timer
		as TX_EXPIRE. i have set the value as 1*HZ.
		the original value should be 60*HZ. you may
		set to any value you feel is good ;p you r rite
		abt the 1 sec part since reading the MII management
		registers is time consuming.
1122:		used TX_EXPIRE instead
1335, 1399, 1428:		
		set next_tick to TX_EXPIRE
1351:		added calls to netif_carrier_on()
1356:		added calls to netif_carrier_off()
1367-1371:	added checking of link state

do let me know if there are any discrepencies.
thanx.

  parent reply	other threads:[~2002-09-17 20:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-17 19:28 [Bonding-devel] Re: Bonding driver unreliable under high CPU load Cureington, Tony
2002-09-17 19:45 ` Jeff Garzik
2002-09-17 19:53   ` [Bonding-devel] Re: Bonding driver unreliable under high CPUload Andrew Morton
2002-09-17 19:58     ` Chad N. Tindel
2002-09-17 20:07       ` Jeff Garzik
2002-09-17 20:11         ` Chad N. Tindel
2002-09-17 20:23           ` Jeff Garzik
2002-09-17 20:11     ` Jeff Garzik
2002-09-17 20:24       ` Andrew Morton
2002-09-17 20:30       ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-17 20:37 Jay Vosburgh

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=3D8790D6.68927887@digeo.com \
    --to=akpm@digeo.com \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=jgarzik@mandrakesoft.com \
    --cc=netdev@oss.sgi.com \
    --cc=pascal.brisset-ml@wanadoo.fr \
    --cc=tony.cureington@hp.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.