From: Chris Mason <chris.mason@oracle.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Fix busyloops in transaction waiting code
Date: Thu, 26 Jan 2012 12:38:05 -0500 [thread overview]
Message-ID: <20120126173805.GU15866@shiny> (raw)
In-Reply-To: <1327594296-23688-1-git-send-email-jack@suse.cz>
On Thu, Jan 26, 2012 at 05:11:36PM +0100, Jan Kara wrote:
> wait_log_commit() and wait_for_writer() were using slightly different
> conditions for deciding whether they should call schedule() and whether they
> should continue in the wait loop. Thus it could happen that we busylooped when
> the first condition was not true while the second one was. That is burning CPU
> cycles needlessly and is deadly on UP machines...
Thanks Jan, I'll pull this in.
-chris
next prev parent reply other threads:[~2012-01-26 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 16:11 [PATCH] btrfs: Fix busyloops in transaction waiting code Jan Kara
2012-01-26 17:38 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-25 14:31 Jan Kara
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=20120126173805.GU15866@shiny \
--to=chris.mason@oracle.com \
--cc=jack@suse.cz \
--cc=linux-btrfs@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).