From: ching <lsching17@gmail.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
dave@jikos.cz
Cc: Liu Bo <bo.li.liu@oracle.com>
Subject: Re: enquiry about autodefrag option
Date: Fri, 21 Sep 2012 05:03:41 +0800 [thread overview]
Message-ID: <505B84AD.7010808@gmail.com> (raw)
In-Reply-To: <20120920115111.GJ17430@twin.jikos.cz>
>> Is there any io niceness control for autodefrag process too? it will
>> be nice if the idle class is used.
> No. Autodefrag will mark file data dirty and they'll be written back to
> the storage in the same way as any other write through the worker
> threads.
>
>
AFAIK, the autodefrag will read related extents and mark them dirty, io niceness should be applicable to the read operation
next prev parent reply other threads:[~2012-09-20 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 11:15 enquiry about autodefrag option (resent) ching
2012-09-19 11:28 ` enquiry about autodefrag option ching
2012-09-19 14:12 ` Liu Bo
2012-09-19 17:39 ` Martin Steigerwald
2012-09-20 14:05 ` David Sterba
2012-09-19 23:36 ` ching
2012-09-20 11:51 ` David Sterba
2012-09-20 21:03 ` ching [this message]
2012-09-24 15:50 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2012-09-17 6:12 ching lu
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=505B84AD.7010808@gmail.com \
--to=lsching17@gmail.com \
--cc=bo.li.liu@oracle.com \
--cc=dave@jikos.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).