From: Frederic Weisbecker <fweisbec@gmail.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Jeff Mahoney <jeffm@suse.com>,
ReiserFS Development List <reiserfs-devel@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>,
Alexander Beregalov <a.beregalov@gmail.com>,
Alessio Igor Bogani <abogani@texware.it>,
J@pimp.vs19.net
Subject: Re: [PATCH 0/6] kill-the-BKL/reiserfs3: performance improvements, faster than Bkl based scheme
Date: Fri, 1 May 2009 16:12:09 +0200 [thread overview]
Message-ID: <20090501141208.GJ6011@nowhere> (raw)
In-Reply-To: <1241180316.3783.3.camel@localhost.localdomain>
On Fri, May 01, 2009 at 02:18:36PM +0200, Thomas Meyer wrote:
> Am Freitag, den 01.05.2009, 07:35 +0200 schrieb Ingo Molnar:
> >
> > I've pulled it and have also merged -rc4 into the kill-the-BKL tree,
> > which can picked up from here:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git core/kill-the-BKL
> >
> > So for comparative benchmarking, vanilla v2.6.30-rc4 (which has the
> > BKL) can be compared against latest kill-the-BKL
>
> Hi,
>
> Kernel gets soft-locked-up in somewhere in initrd:
>
> See
> http://m3y3r.de/bilder/img_0524.jpg
> http://m3y3r.de/bilder/img_0525.jpg
> http://m3y3r.de/bilder/img_0526.jpg
> http://m3y3r.de/bilder/img_0527.jpg
> http://m3y3r.de/bilder/img_0528.jpg
> http://m3y3r.de/bilder/img_0529.jpg
Looks like someone owns the kernel lock and is sleeping
with the assumption it releases the lock, like the old bkl did.
> config is:
> http://m3y3r.de/bilder/config-2.6.30-rc4-ktb
Thanks, I will try it out once I have some time.
> greets
> thomas
>
>
next prev parent reply other threads:[~2009-05-01 14:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 2:44 [PATCH 0/6] kill-the-BKL/reiserfs3: performance improvements, faster than Bkl based scheme Frederic Weisbecker
2009-05-01 2:44 ` [PATCH 1/6] kill-the-BKL/reiserfs: release write lock on fs_changed() Frederic Weisbecker
2009-05-01 6:31 ` Andi Kleen
2009-05-01 13:28 ` Frederic Weisbecker
2009-05-01 13:44 ` Chris Mason
2009-05-01 14:01 ` Frederic Weisbecker
2009-05-01 14:14 ` Chris Mason
2009-05-02 1:19 ` Frederic Weisbecker
2009-05-01 2:44 ` [PATCH 2/6] kill-the-BKL/reiserfs: release the write lock before rescheduling on do_journal_end() Frederic Weisbecker
2009-05-01 7:09 ` Ingo Molnar
2009-05-01 13:31 ` Frederic Weisbecker
2009-05-01 22:20 ` Frederic Weisbecker
2009-05-01 2:44 ` [PATCH 3/6] kill-the-BKL/reiserfs: release write lock while rescheduling on prepare_for_delete_or_cut() Frederic Weisbecker
2009-05-01 2:44 ` [PATCH 4/6] kill-the-BKL/reiserfs: release the write lock inside get_neighbors() Frederic Weisbecker
2009-05-01 5:51 ` Ingo Molnar
2009-05-01 13:25 ` Frederic Weisbecker
2009-05-01 13:29 ` Chris Mason
2009-05-01 13:31 ` Ingo Molnar
2009-05-01 2:44 ` [PATCH 5/6] kill-the-BKL/reiserfs: release the write lock inside reiserfs_read_bitmap_block() Frederic Weisbecker
2009-05-01 5:47 ` Ingo Molnar
2009-05-01 13:19 ` Frederic Weisbecker
2009-05-01 13:30 ` Chris Mason
2009-05-01 13:51 ` Frederic Weisbecker
2009-05-01 2:44 ` [PATCH 6/6] kill-the-BKL/reiserfs: release the write lock on flush_commit_list() Frederic Weisbecker
2009-05-01 5:42 ` Ingo Molnar
2009-05-01 13:13 ` Frederic Weisbecker
2009-05-01 13:23 ` Ingo Molnar
2009-05-01 13:26 ` Chris Mason
2009-05-01 13:29 ` Ingo Molnar
2009-05-01 13:54 ` Chris Mason
2009-05-01 5:35 ` [PATCH 0/6] kill-the-BKL/reiserfs3: performance improvements, faster than Bkl based scheme Ingo Molnar
2009-05-01 12:18 ` Thomas Meyer
2009-05-01 14:12 ` Frederic Weisbecker [this message]
2009-05-01 19:59 ` Linus Torvalds
2009-05-01 20:33 ` Ingo Molnar
2009-05-01 20:36 ` Ingo Molnar
2009-05-01 21:11 ` Linus Torvalds
2009-05-01 21:32 ` Ingo Molnar
2009-05-02 1:39 ` Frederic Weisbecker
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=20090501141208.GJ6011@nowhere \
--to=fweisbec@gmail.com \
--cc=J@pimp.vs19.net \
--cc=a.beregalov@gmail.com \
--cc=abogani@texware.it \
--cc=chris.mason@oracle.com \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=reiserfs-devel@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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