From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: linux-mm@kvack.org
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v8 1/2] sb: add a new writeback list for sync
Date: Wed, 22 Jun 2016 12:46:35 +0000 (UTC) [thread overview]
Message-ID: <pan$a4de2$c46ac11d$189b022f$c3599939@applied-asynchrony.com> (raw)
In-Reply-To: 1466594593-6757-2-git-send-email-bfoster@redhat.com
On Wed, 22 Jun 2016 07:23:12 -0400, Brian Foster wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> wait_sb_inodes() currently does a walk of all inodes in the
> filesystem to find dirty one to wait on during sync. This is highly
> inefficient and wastes a lot of CPU when there are lots of clean
> cached inodes that we don't need to wait on.
(..)
> Tested-by: Holger HoffstA?tte <holger.hoffstaette@applied-asynchrony.com>
Brian alerted me to the fact that I'm confused, so for the record this
should have been:
Tested-by: Holger HoffstA?tte <holger@applied-asynchrony.com>
sorry..ETOOMANYADDRS :(
-h
--
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:[~2016-06-22 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 11:23 [PATCH v8 0/2] improve sync efficiency with sb inode wb list Brian Foster
2016-06-22 11:23 ` [PATCH v8 1/2] sb: add a new writeback list for sync Brian Foster
2016-06-22 12:46 ` Holger Hoffstätte [this message]
2016-06-22 11:23 ` [PATCH v8 2/2] wb: inode writeback list tracking tracepoints Brian Foster
2016-06-22 13:12 ` [PATCH v8 0/2] improve sync efficiency with sb inode wb list 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='pan$a4de2$c46ac11d$189b022f$c3599939@applied-asynchrony.com' \
--to=holger@applied-asynchrony.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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).