public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: "Hen, Shmulik" <shmulik.hen@intel.com>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>
Subject: Re: spinlock help
Date: Wed, 07 Mar 2001 23:53:34 +1100	[thread overview]
Message-ID: <3AA62F4E.AB901CBB@uow.edu.au> (raw)
In-Reply-To: <07E6E3B8C072D211AC4100A0C9C5758302B27157@hasmsx52.iil.intel.com>

"Hen, Shmulik" wrote:
> 
> The kdb trace was accurate, we could actually see the e100 ISR pop from no
> where right in the middle of our ans_notify every time the TX queue would
> fill up. When we commented out the call to spin_*_irqsave(), it worked fine
> under heavy stress for days.
> 
> Is it possible it was something wrong with 2.4.0-test10 specifically ?
> 

Sorry, no.  If spin_lock_irqsave()/spin_unlock_irqrestore()
were accidentally reenabling interrupts then it would be
the biggest, ugliest catastrophe since someone put out a kernel
which forgot to flush dirty inodes to disk :)

Conceivably it was a compiler bug.  Were you using egcs-1.1.2/x86?

-

  reply	other threads:[~2001-03-07 12:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-07 12:26 spinlock help Hen, Shmulik
2001-03-07 12:53 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-08 11:07 Hen, Shmulik
2001-03-08 11:34 ` Andrew Morton
2001-03-07 16:54 Ofer Fryman
2001-03-07 10:46 Hen, Shmulik
2001-03-07 10:44 Hen, Shmulik
2001-03-07 13:19 ` Alan Cox
2001-03-07 10:31 Ofer Fryman
2001-03-07  9:21 Hen, Shmulik
2001-03-07 10:26 ` Manoj Sontakke
2001-03-06 14:05 Manoj Sontakke
2001-03-06 23:53 ` Nigel Gamble

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=3AA62F4E.AB901CBB@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shmulik.hen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox