From: Jens Axboe <axboe@kernel.dk>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCHv6 00/15] kill unnecessary bdi wakeups + cleanups
Date: Tue, 03 Aug 2010 14:27:08 +0200 [thread overview]
Message-ID: <4C580B1C.3020409@kernel.dk> (raw)
In-Reply-To: <1280057365-10297-1-git-send-email-dedekind1@gmail.com>
On 2010-07-25 13:29, Artem Bityutskiy wrote:
> Hi,
>
> here is v6 of the patch series which clean-ups bdi threads and substantially
> lessens amount of unnecessary kernel wake-ups, which is very important on
> battery-powered devices.
>
> This patch-set is also available at:
> git://git.infradead.org/users/dedekind/misc-2.6.git flushers_v6
Thanks Artem, for sticking around long enough to get this into
shape. I have finally merged it.
> 1. Use 'spin_lock_bh' for the 'bdi->wb_lock' (changed patch N12)
I'd rather not, question is how to avoid it. Either just wakeup the
default thread, or punt the lock-and-check bdi->wb.task to a thread.
--
Jens Axboe
next prev parent reply other threads:[~2010-08-03 12:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 11:29 [PATCHv6 00/15] kill unnecessary bdi wakeups + cleanups Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 01/15] writeback: harmonize writeback threads naming Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 02/15] writeback: fix possible race when creating bdi threads Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 03/15] writeback: do not lose wake-ups in the forker thread - 1 Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 04/15] writeback: do not lose wake-ups in the forker thread - 2 Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 05/15] writeback: do not lose wake-ups in bdi threads Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 06/15] writeback: simplify bdi code a little Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 07/15] writeback: do not remove bdi from bdi_list Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 08/15] writeback: move last_active to bdi Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 09/15] writeback: restructure bdi forker loop a little Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 10/15] writeback: move bdi threads exiting logic to the forker thread Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 11/15] writeback: prevent unnecessary bdi threads wakeups Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 12/15] writeback: optimize periodic bdi thread wakeups Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 13/15] writeback: remove unnecessary init_timer call Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 14/15] writeback: add new tracepoints Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 15/15] writeback: cleanup bdi_register Artem Bityutskiy
2010-08-03 4:44 ` [PATCHv6 00/15] kill unnecessary bdi wakeups + cleanups Artem Bityutskiy
2010-08-03 12:27 ` Jens Axboe [this message]
2010-08-03 12:37 ` Artem Bityutskiy
2010-08-03 12:47 ` Jens Axboe
2010-08-04 11:34 ` Jens Axboe
2010-08-05 9:35 ` Artem Bityutskiy
2010-08-03 14:11 ` Artem Bityutskiy
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=4C580B1C.3020409@kernel.dk \
--to=axboe@kernel.dk \
--cc=dedekind1@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).