From: "Ken Chen" <kenchen@google.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Zhao Forrest <forrest.zhao@gmail.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Why kmem_cache_free occupy CPU for more than 10 seconds?
Date: Wed, 11 Apr 2007 09:35:39 -0700 [thread overview]
Message-ID: <b040c32a0704110935k1723c85ay4a862539bad56c05@mail.gmail.com> (raw)
In-Reply-To: <1176287911.6893.47.camel@twins>
On 4/11/07, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Wed, 2007-04-11 at 17:53 +0800, Zhao Forrest wrote:
> > I got some new information:
> > Before soft lockup message is out, we have:
> > [root@nsgsh-dhcp-149 home]# cat /proc/slabinfo |grep buffer_head
> > buffer_head 10927942 10942560 120 32 1 : tunables 32
> > 16 8 : slabdata 341955 341955 6 : globalstat 37602996 11589379
> > 1174373 6 0 1 6918 12166031 1013708
> > : cpustat 35254590 2350698 13610965 907286
> >
> > Then after buffer_head is freed, we have:
> > [root@nsgsh-dhcp-149 home]# cat /proc/slabinfo |grep buffer_head
> > buffer_head 9542 36384 120 32 1 : tunables 32 16
> > 8 : slabdata 1137 1137 245 : globalstat 37602996 11589379
> > 1174373 6 0 1 6983 20507478
> > 1708818 : cpustat 35254625 2350704 16027174 1068367
> >
> > Does this huge number of buffer_head cause the soft lockup?
>
> __blkdev_put() takes the BKL and bd_mutex
> invalidate_mapping_pages() tries to take the PageLock
>
> But no other looks seem held while free_buffer_head() is called
>
> All these locks are preemptible (CONFIG_PREEMPT_BKL?=y) and should not
> hog the cpu like that, what preemption mode have you got selected?
> (CONFIG_PREEMPT_VOLUNTARY?=y)
also, you can try this patch:
http://groups.google.com/group/linux.kernel/browse_thread/thread/7086e4b9d5504dc9/c608bfea4614b07e?lnk=gst&q=+Big+kernel+lock+contention+in+do_open&rnum=1#c608bfea4614b07e
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-04-11 16:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 6:17 Zhao Forrest
2007-04-11 6:53 ` Pekka Enberg
2007-04-11 9:14 ` Zhao Forrest
2007-04-11 9:53 ` Paul Jackson
2007-04-11 10:06 ` Peter Zijlstra
2007-04-11 10:10 ` Zhao Forrest
2007-04-11 10:16 ` Peter Zijlstra
2007-04-11 16:23 ` Chuck Ebbert
2007-04-11 16:44 ` Badari Pulavarty
2007-04-11 9:53 ` Zhao Forrest
2007-04-11 10:38 ` Peter Zijlstra
2007-04-11 16:35 ` Ken Chen [this message]
2007-04-12 6:17 ` Zhao Forrest
2007-04-11 22:30 ` Andrew Morton
2007-04-12 7:39 ` Peter Zijlstra
2007-04-12 7:55 ` Andrew Morton
2007-04-12 9:19 ` Peter Zijlstra
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=b040c32a0704110935k1723c85ay4a862539bad56c05@mail.gmail.com \
--to=kenchen@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=forrest.zhao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
/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