From: John Hughes <john@Calva.COM>
To: Andre Noll <maan@systemlinux.org>
Cc: Jens Axboe <jens.axboe@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 15426] New: Running many copies of bonnie++ on different filesystems seems to deadlock in sync
Date: Fri, 05 Mar 2010 11:44:01 +0100 [thread overview]
Message-ID: <4B90E071.1060903@Calva.COM> (raw)
In-Reply-To: <20100304174239.GO7517@skl-net.de>
Andre Noll wrote:
> On 15:55, John Hughes wrote:
>
>>> That's the same patch you posted two weeks ago and on which Linus
>>> commented he thinks it is broken. He also proposed another, simpler
>>> patch (included below) which I'm running for a few days and which
>>> fixes the sync problem for me.
>>>
>>>
>> I've tried the "simpler patch" on my system and it makes no difference
>> for me.
>>
>
> Does it make no difference to Jens' patch, or no difference to an
> unpatched kernel?
>
No difference to an unpatched kernel. I didn't think of stacking the
patches.
> BTW, switching from cfq to noop or deadline also improved things a
> bit for me.
>
Will try that.
next prev parent reply other threads:[~2010-03-05 10:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15426-10286@http.bugzilla.kernel.org/>
2010-03-03 0:16 ` [Bugme-new] [Bug 15426] New: Running many copies of bonnie++ on different filesystems seems to deadlock in sync Andrew Morton
2010-03-03 12:09 ` John Hughes
2010-03-03 11:50 ` Jens Axboe
2010-03-03 12:37 ` John Hughes
2010-03-03 12:03 ` Jens Axboe
2010-03-03 12:45 ` John Hughes
2010-03-03 12:09 ` Jens Axboe
2010-03-03 14:42 ` Andre Noll
2010-03-04 14:55 ` John Hughes
2010-03-04 17:42 ` Andre Noll
2010-03-05 10:44 ` John Hughes [this message]
2010-03-03 18:33 ` John Hughes
2010-03-04 11:16 ` John Hughes
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=4B90E071.1060903@Calva.COM \
--to=john@calva.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maan@systemlinux.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).