linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, MPatlasov@parallels.com,
	fengguang.wu@intel.com, hmh@hmh.eng.br, jack@suse.cz,
	mel@csn.ul.ie, t.artem@lycos.com, tytso@mit.edu
Subject: Re: [patch 15/15] mm: add strictlimit knob
Date: Fri, 1 Dec 2017 13:29:28 +0100	[thread overview]
Message-ID: <20171201122928.GD8365@quack2.suse.cz> (raw)
In-Reply-To: <5a20831e./7a6H+akjTcq4WCk%akpm@linux-foundation.org>

On Thu 30-11-17 14:15:58, Andrew Morton wrote:
> From: Maxim Patlasov <MPatlasov@parallels.com>
> Subject: mm: add strictlimit knob
> 
> The "strictlimit" feature was introduced to enforce per-bdi dirty limits
> for FUSE which sets bdi max_ratio to 1% by default:
> 
> http://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 /sys/class/bdi/X:Y/max_ratio is decreased to some reasonable value.

In principle I have nothing against this and the usecase sounds reasonable
(in fact I believe the lack of a feature like this is one of reasons why
desktop automounters usually mount USB devices with 'sync' mount option).
So feel free to add:

Reviewed-by: Jan Kara <jack@suse.cz>

								Honza

> Signed-off-by: Maxim Patlasov <MPatlasov@parallels.com>
> Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> Cc: Theodore Ts'o <tytso@mit.edu>
> Cc: "Artem S. Tashkinov" <t.artem@lycos.com>
> Cc: Mel Gorman <mel@csn.ul.ie>
> Cc: Jan Kara <jack@suse.cz>
> Cc: Wu Fengguang <fengguang.wu@intel.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  Documentation/ABI/testing/sysfs-class-bdi |    8 ++++
>  mm/backing-dev.c                          |   35 ++++++++++++++++++++
>  2 files changed, 43 insertions(+)
> 
> diff -puN Documentation/ABI/testing/sysfs-class-bdi~mm-add-strictlimit-knob-v2 Documentation/ABI/testing/sysfs-class-bdi
> --- a/Documentation/ABI/testing/sysfs-class-bdi~mm-add-strictlimit-knob-v2
> +++ a/Documentation/ABI/testing/sysfs-class-bdi
> @@ -53,3 +53,11 @@ stable_pages_required (read-only)
>  
>  	If set, the backing device requires that all pages comprising a write
>  	request must not be changed until writeout is complete.
> +
> +strictlimit (read-write)
> +
> +	Forces per-BDI checks for the share of given device in the write-back
> +	cache even before the global background dirty limit is reached. This
> +	is useful in situations where the global limit is much higher than
> +	affordable for given relatively slow (or untrusted) device. Turning
> +	strictlimit on has no visible effect if max_ratio is equal to 100%.
> diff -puN mm/backing-dev.c~mm-add-strictlimit-knob-v2 mm/backing-dev.c
> --- a/mm/backing-dev.c~mm-add-strictlimit-knob-v2
> +++ a/mm/backing-dev.c
> @@ -218,11 +218,46 @@ static ssize_t stable_pages_required_sho
>  }
>  static DEVICE_ATTR_RO(stable_pages_required);
>  
> +static ssize_t strictlimit_store(struct device *dev,
> +		struct device_attribute *attr, const char *buf, size_t count)
> +{
> +	struct backing_dev_info *bdi = dev_get_drvdata(dev);
> +	unsigned int val;
> +	ssize_t ret;
> +
> +	ret = kstrtouint(buf, 10, &val);
> +	if (ret < 0)
> +		return ret;
> +
> +	switch (val) {
> +	case 0:
> +		bdi->capabilities &= ~BDI_CAP_STRICTLIMIT;
> +		break;
> +	case 1:
> +		bdi->capabilities |= BDI_CAP_STRICTLIMIT;
> +		break;
> +	default:
> +		return -EINVAL;
> +	}
> +
> +	return count;
> +}
> +static ssize_t strictlimit_show(struct device *dev,
> +		struct device_attribute *attr, char *page)
> +{
> +	struct backing_dev_info *bdi = dev_get_drvdata(dev);
> +
> +	return snprintf(page, PAGE_SIZE-1, "%d\n",
> +			!!(bdi->capabilities & BDI_CAP_STRICTLIMIT));
> +}
> +static DEVICE_ATTR_RW(strictlimit);
> +
>  static struct attribute *bdi_dev_attrs[] = {
>  	&dev_attr_read_ahead_kb.attr,
>  	&dev_attr_min_ratio.attr,
>  	&dev_attr_max_ratio.attr,
>  	&dev_attr_stable_pages_required.attr,
> +	&dev_attr_strictlimit.attr,
>  	NULL,
>  };
>  ATTRIBUTE_GROUPS(bdi_dev);
> _
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

--
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>

  reply	other threads:[~2017-12-01 12:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 22:15 [patch 15/15] mm: add strictlimit knob akpm
2017-12-01 12:29 ` Jan Kara [this message]
2017-12-07  1:09   ` Andrew Morton
2017-12-07  4:14     ` Fengguang Wu
2017-12-07  8:50       ` Miklos Szeredi
2017-12-07 10:15         ` Fengguang Wu
2017-12-07 10:32           ` Miklos Szeredi
2018-01-31 22:58             ` 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=20171201122928.GD8365@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=MPatlasov@parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=hmh@hmh.eng.br \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=t.artem@lycos.com \
    --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;
as well as URLs for NNTP newsgroup(s).