From: Maxim Patlasov <mpatlasov@parallels.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: karl.kiniger@med.ge.com, jack@suse.cz,
linux-kernel@vger.kernel.org, t.artem@lycos.com,
linux-mm@kvack.org, mgorman@suse.de, tytso@mit.edu,
fengguang.wu@intel.com, torvalds@linux-foundation.org
Subject: Re: [PATCH] mm: add strictlimit knob
Date: Wed, 6 Nov 2013 18:30:01 +0400 [thread overview]
Message-ID: <527A5269.7040900@parallels.com> (raw)
In-Reply-To: <20131104140104.7936d263258a7a6753eb325e@linux-foundation.org>
Hi Andrew,
On 11/05/2013 02:01 AM, Andrew Morton wrote:
> On Fri, 01 Nov 2013 18:31:40 +0400 Maxim Patlasov <MPatlasov@parallels.com> wrote:
>
>> "strictlimit" feature was introduced to enforce per-bdi dirty limits for
>> FUSE which sets bdi max_ratio to 1% by default:
>>
>> http://www.http.com//article.gmane.org/gmane.linux.kernel.mm/105809
>>
>> However the feature can be useful for other relatively slow or untrusted
>> BDIs like USB flash drives and DVD+RW. The patch adds a knob to enable the
>> feature:
>>
>> echo 1 > /sys/class/bdi/X:Y/strictlimit
>>
>> Being enabled, the feature enforces bdi max_ratio limit even if global (10%)
>> dirty limit is not reached. Of course, the effect is not visible until
>> max_ratio is decreased to some reasonable value.
> I suggest replacing "max_ratio" here with the much more informative
> "/sys/class/bdi/X:Y/max_ratio".
>
> Also, Documentation/ABI/testing/sysfs-class-bdi will need an update
> please.
OK, I'll update it, fix patch description and re-send the patch.
>
>> mm/backing-dev.c | 35 +++++++++++++++++++++++++++++++++++
>> 1 file changed, 35 insertions(+)
>>
> I'm not really sure what to make of the patch. I assume you tested it
> and observed some effect. Could you please describe the test setup and
> the effects in some detail?
I plugged 16GB USB-flash in a node with 8GB RAM running 3.12.0-rc7 and
started writing a huge file by "dd" (from /dev/zero to USB-flash
mount-point). While writing I was observing "Dirty" counter as reported
by /proc/meminfo. As expected it stabilized on a level about 1.2GB (15%
of total RAM). Immediately after dd completed, the "umount" command took
about 5 minutes. This corresponded to 5MB write throughput of the flash
drive.
Then I repeated the experiment after setting tunables:
echo 1 > /sys/class/bdi/8\:16/max_ratio
echo 1 > /sys/class/bdi/8\:16/strictlimit
This time, "Dirty" counter became 100 times lesser - about 12MB and
"umount" took about a second.
Thanks,
Maxim
--
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:[~2013-11-06 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131031142612.GA28003@kipc2.localdomain>
2013-11-01 14:31 ` Maxim Patlasov
2013-11-04 22:01 ` Andrew Morton
2013-11-06 14:30 ` Maxim Patlasov [this message]
2013-11-06 15:05 ` [PATCH] mm: add strictlimit knob -v2 Maxim Patlasov
2013-11-07 12:26 ` Henrique de Moraes Holschuh
2013-11-22 23:45 ` Andrew Morton
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=527A5269.7040900@parallels.com \
--to=mpatlasov@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=karl.kiniger@med.ge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=t.artem@lycos.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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