All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe W Damasio <felipewd@terra.com.br>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: linux-kernel@vger.kernel.org, rnp@netlink.co.nz
Subject: Re: [PATCH] Fix SMP support on 3c527 net driver
Date: Sun, 31 Aug 2003 13:50:30 -0300	[thread overview]
Message-ID: <3F522756.9000105@terra.com.br> (raw)
In-Reply-To: <3F51B1A3.4080307@colorfullife.com>

	Hi Manfred,

Manfred Spraul wrote:
> Additionally, you must replace the sleep_on calls with wait_event, or an 
> open-coded wait queue: sleep_on is racy, it only works with cli().

	Oh, I didn't no that..

> IMHO the right way to fix cli() is
> - add a single spinlock to the driver or the device structure. Do not 
> forget the spin_lock_init().
> - replace cli/sti with spin_lock_irqsave/spin_unlock_irqsave.

	Yes.

> - Additionally acquire the spinlock in every interrupt handler (cli() 
> stops all interrupts, spinlocks only stop interrupt on the current cpu).
> - check if there were recursive cli() calls. Fix them.
> - replace all sleep_on calls with wait queue calls.
> - check if there are any kmalloc or schedule calls in the area now under 
> the spinlock, and reorganize the code.

	But doesn't wait_queue call schedule()?

> And please add a changelog entry that code was converted without testing.

	Ok.

	Thanks for your review, will work on those.

Felipe
-- 
It's most certainly GNU/Linux, not Linux. Read more at
http://www.gnu.org/gnu/why-gnu-linux.html


  reply	other threads:[~2003-08-31 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-31  8:28 [PATCH] Fix SMP support on 3c527 net driver Manfred Spraul
2003-08-31 16:50 ` Felipe W Damasio [this message]
2003-08-31 17:30   ` Manfred Spraul
  -- strict thread matches above, loose matches on Subject: below --
2003-08-31  3:06 Felipe W Damasio

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=3F522756.9000105@terra.com.br \
    --to=felipewd@terra.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=rnp@netlink.co.nz \
    /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.