From: Brian Tinsley <btinsley@emageon.com>
To: Paul Jakma <paulj@alphyra.ie>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.20, .text.lock.swap cpu usage? (ibm x440) [rescued]
Date: Sun, 12 Jan 2003 21:41:35 -0600 [thread overview]
Message-ID: <3E22356F.2000205@emageon.com> (raw)
In-Reply-To: Pine.LNX.4.44.0301130257020.26185-100000@dunlop.admin.ie.alphyra.com
>
>
>Which driver are you using for the QLA23xx?
>
The 6.01.00-fo driver from QLogic.
>I've missed the beginning of this thread, but problem here may not
>have anything to with the number of threads you're runnng, rather it
>may well be the qla2300 driver, if you are using the qlogic v6 driver.
>
I was getting nailed by an issue involving reaping inodes (or the lack
thereof). I don't believe the QLogic driver was contributing to my
problem. I've had this driver running in my lab and at numerous client
sites for quite some time and have never seen it even burp.
>I have a test system in work which is similar to yours (2x qla2310F,
>SMP (dual athlon) attached to FC RAID storage) and it is easy to live
>lock with any kind of intensive IO, eg bonnie++.
>
>The Redhat 5.31-RH driver is about the most stable one, but i havnt
>extensively stress tested it. All of the qlogic v6 drivers are trivial
>to lock. (they spin forever in the qla2300 ISR - qlogic have beta
>drivers, but they still have the same problem).
>
Interesting. Again, I've never seen this behavior, but I appreciate your
mentioning it. It's definitely something to keep an eye out for.
--
Brian Tinsley
Chief Systems Engineer
Emageon
next parent reply other threads:[~2003-01-13 3:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0301130257020.26185-100000@dunlop.admin.ie.alphyra.com>
2003-01-13 3:41 ` Brian Tinsley [this message]
2003-01-13 5:46 ` qla2300 driver stability, (was Re: 2.4.20, .text.lock.swap cpu usage?) Paul Jakma
2003-01-10 18:38 2.4.20, .text.lock.swap cpu usage? (ibm x440) [rescued] Brian Tinsley
-- strict thread matches above, loose matches on Subject: below --
2003-01-10 18:38 Martin J. Bligh
2003-01-10 18:34 Brian Tinsley
2003-01-10 18:34 Brian Tinsley
2003-01-10 18:33 William Lee Irwin III
2003-01-10 18:32 William Lee Irwin III
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=3E22356F.2000205@emageon.com \
--to=btinsley@emageon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulj@alphyra.ie \
/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