From: Alexander Hoogerhuis <alexh@ihatent.com>
To: Stephen Evanchik <evanchsa@clarkson.edu>
Cc: Benjamin LaHaise <bcrl@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5.54] hermes: serialization fixes
Date: 06 Jan 2003 18:40:17 +0100 [thread overview]
Message-ID: <878yxyqiri.fsf@lapper.ihatent.com> (raw)
In-Reply-To: <200301031256.41451.evanchsa@clarkson.edu>
Stephen Evanchik <evanchsa@clarkson.edu> writes:
> On Friday 03 January 2003 12:47, you wrote:
> | Why not put the spinlock/unlock inside hermes_bap_seek()? Smaller, better
> | contained and more readable.
>
> That's the better solution, I'm trying to coordinate a bit with the
> maintainer. The only reason I didn't do this in the first place is because
> there is a (possibly unecessary) delay loop inside hermes_bap_seek that I
> believe is trying to combat the same problem. I'm awaiting a response from
> the maintainer since he knows a bit more about the hardware than I do.
>
There is something not quite right about this patch. I used have a ton
of errors in my logs, and this patch seemed to clear this out nicely.
When I run with a patched driver now, I run for about 20 minutes with
various loads and sudenly the ksoftirqd_CPU0 process starts to hog my
CPU and not wanting to let go. As soon as I pull out the card, the
load returns to normal.
Is there any way I can provide more details on what is happening?
>
> Stephen
>
mvh,
A
--
Alexander Hoogerhuis | alexh@ihatent.com
CCNP - CCDP - MCNE - CCSE | +47 908 21 485
"You have zero privacy anyway. Get over it." --Scott McNealy
next prev parent reply other threads:[~2003-01-06 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 17:39 [PATCH 2.5.54] hermes: serialization fixes Stephen Evanchik
2003-01-03 17:47 ` Benjamin LaHaise
2003-01-03 17:56 ` Stephen Evanchik
2003-01-06 17:40 ` Alexander Hoogerhuis [this message]
2003-01-06 18:36 ` Stephen Evanchik
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=878yxyqiri.fsf@lapper.ihatent.com \
--to=alexh@ihatent.com \
--cc=bcrl@redhat.com \
--cc=evanchsa@clarkson.edu \
--cc=linux-kernel@vger.kernel.org \
/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