From: Rick Jones <rick.jones2@hp.com>
To: Divy Le Ray <divy@chelsio.com>
Cc: Linux Network Development list <netdev@vger.kernel.org>,
linux-ia64@vger.kernel.org
Subject: Re: Soft Lockups on 2.6.28-rc8 under netperf bulk receive workload
Date: Wed, 17 Dec 2008 11:44:09 -0800 [thread overview]
Message-ID: <49495689.9090205@hp.com> (raw)
In-Reply-To: <494934C5.5000003@chelsio.com>
Divy Le Ray wrote:
> Can you please reconfigure your kernel with the following kernel hacking
> options enabled, and run your tests again?
>
> Kernel hacking
> Kernel debugging
> Detect soft lockups
> RT mutex debugging
> Spinlock and rw-lock debugging: basic checks
> Mutex debugging: basic checks
Got the above
> Lock debugging: detect incorrect freeing of live locks
> Lock debugging: prove locking correctness
I don't see those two above in a make menuconfig
> Spinlock debugging: sleep-inside-spinlock checking
> Compile the kernel with debug info
Got those above.
> Compile the kernel with frame pointers
That doesn't appear in make menuconfig in kernel hacking either.
I built a kernel with those I could find enabled, and I think it invoked
the spirit of Heisenberg - no more soft lockups appearing on the
console. I think it has also _significantly_ dropped the throughput.
I've since learned how to tell caliper one doesn't care about the
per-process stuff and just lump it all together. The cycles and cgprof
profiles for the debug run can be found under the same URL as before:
ftp://ftp.netperf.org/lockup
with what I hope are obvious names.
rick jones
prev parent reply other threads:[~2008-12-17 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 1:31 Soft Lockups on 2.6.28-rc8 under netperf bulk receive workload Rick Jones
2008-12-17 17:20 ` Divy Le Ray
2008-12-17 19:44 ` Rick Jones [this message]
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=49495689.9090205@hp.com \
--to=rick.jones2@hp.com \
--cc=divy@chelsio.com \
--cc=linux-ia64@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).