All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Chad N. Tindel" <ctindel@falcon.csc.calpoly.edu>
Cc: Andrew Morton <akpm@digeo.com>,
	"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 16:23:52 -0400	[thread overview]
Message-ID: <3D878F58.7060706@mandrakesoft.com> (raw)
In-Reply-To: Pine.GSO.4.44.0209171311080.11147-100000@falcon.csc.calpoly.edu

Chad N. Tindel wrote:
>>>Will netif_carrier_ok(slave_dev) always work?  Do all drivers support the
>>>__LINK_STATE_NOCARRIER flag?
>>
>>
>>No.  Read again the precise language I used :)
> 
> 
> Right, well thats what I thought.  But how can we do what Andrew wants?


You'll need execute those ioctls from process context -- or call 
dev->do_ioctl() yourself with proper locking.  The latter would 
certainly be faster but you must be _very_ careful to avoid deadlocks. 
The former would certainly be preferred anyway, because calling an ioctl 
to check link state means you are hitting the slave_dev's phy, which is 
a very expensive operation in and of itself.

Unfortunately I am thinking that locking in bonding.c may need a 
re-think if you want to do this sort of stuff :(  Semaphores instead of 
a spinlocks may be appropriate, depending on the contexts in which 
link_state _really_ needs to be checked.

	Jeff

  reply	other threads:[~2002-09-17 20:23 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 [this message]
2002-09-17 20:11     ` Jeff Garzik
2002-09-17 20:24       ` Andrew Morton
2002-09-17 20:30       ` Andrew Morton
  -- 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=3D878F58.7060706@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=akpm@digeo.com \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=ctindel@falcon.csc.calpoly.edu \
    --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.