From: Boaz Harrosh <bharrosh@panasas.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: <axboe@kernel.dk>, <lucho@ionkov.net>, <tytso@mit.edu>,
<sage@inktank.com>, <ericvh@gmail.com>, <mfasheh@suse.com>,
<dedekind1@gmail.com>, <adrian.hunter@intel.com>,
<dhowells@redhat.com>, <sfrench@samba.org>, <jlbec@evilplan.org>,
<rminnich@sandia.gov>, <linux-cifs@vger.kernel.org>,
<jack@suse.cz>, <martin.petersen@oracle.com>, <neilb@suse.de>,
<david@fromorbit.com>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-mtd@lists.infradead.org>,
<linux-fsdevel@vger.kernel.org>,
<v9fs-developer@lists.sourceforge.net>,
<ceph-devel@vger.kernel.org>, <linux-ext4@vger.kernel.org>,
<linux-afs@lists.infradead.org>, <ocfs2-devel@oss.oracle.com>
Subject: Re: [PATCH 1/3] bdi: Track users that require stable page writes
Date: Thu, 1 Nov 2012 11:21:22 -0700 [thread overview]
Message-ID: <5092BDA2.6090001@panasas.com> (raw)
In-Reply-To: <20121101075813.16153.94581.stgit@blackbox.djwong.org>
On 11/01/2012 12:58 AM, Darrick J. Wong wrote:
> This creates a per-backing-device counter that tracks the number of users which
> require pages to be held immutable during writeout. Eventually it will be used
> to waive wait_for_page_writeback() if nobody requires stable pages.
>
There is two things I do not like:
1. Please remind me why we need the users counter?
If the device needs it, it will always be needed. The below
queue_unrequire_stable_pages call at blk_integrity_unregister
only happens at device destruction time, no?
It was also said that maybe individual filesystems would need
stable pages where other FSs using the same BDI do not. But
since the FS is at the driving seat in any case, it can just
do wait_for_writeback() regardless and can care less about
the bdi flag and the other FSs. Actually all those FSs already
do this this, and do not need any help. So this reason is
mute.
2. I hate the atomic_read for every mkwrite. I think we can do
better, since as you noted it can never be turned off, only
on, at init time. And because of 1. above it is not dynamic.
I think I like your previous simple bool better.
But I do like a lot the new request_queue API you added here.
Thanks
Boaz
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> Documentation/ABI/testing/sysfs-class-bdi | 7 +++++
> block/blk-integrity.c | 4 +++
> include/linux/backing-dev.h | 16 ++++++++++++
> include/linux/blkdev.h | 10 ++++++++
> mm/backing-dev.c | 38 +++++++++++++++++++++++++++++
> 5 files changed, 75 insertions(+)
>
>
> diff --git a/Documentation/ABI/testing/sysfs-class-bdi b/Documentation/ABI/testing/sysfs-class-bdi
> index 5f50097..218a618 100644
> --- a/Documentation/ABI/testing/sysfs-class-bdi
> +++ b/Documentation/ABI/testing/sysfs-class-bdi
> @@ -48,3 +48,10 @@ max_ratio (read-write)
> most of the write-back cache. For example in case of an NFS
> mount that is prone to get stuck, or a FUSE mount which cannot
> be trusted to play fair.
> +
> +stable_pages_required (read-write)
> +
> + If set, the backing device requires that all pages comprising a write
> + request must not be changed until writeout is complete. The system
> + administrator can turn this on if the hardware does not do so already.
> + However, once enabled, this flag cannot be disabled.
> diff --git a/block/blk-integrity.c b/block/blk-integrity.c
> index da2a818..cf2dd95 100644
> --- a/block/blk-integrity.c
> +++ b/block/blk-integrity.c
> @@ -420,6 +420,8 @@ int blk_integrity_register(struct gendisk *disk, struct blk_integrity *template)
> } else
> bi->name = bi_unsupported_name;
>
> + queue_require_stable_pages(disk->queue);
> +
> return 0;
> }
> EXPORT_SYMBOL(blk_integrity_register);
> @@ -438,6 +440,8 @@ void blk_integrity_unregister(struct gendisk *disk)
> if (!disk || !disk->integrity)
> return;
>
> + queue_unrequire_stable_pages(disk->queue);
> +
> bi = disk->integrity;
>
> kobject_uevent(&bi->kobj, KOBJ_REMOVE);
> diff --git a/include/linux/backing-dev.h b/include/linux/backing-dev.h
> index 2a9a9ab..0554f5d 100644
> --- a/include/linux/backing-dev.h
> +++ b/include/linux/backing-dev.h
> @@ -109,6 +109,7 @@ struct backing_dev_info {
> struct dentry *debug_dir;
> struct dentry *debug_stats;
> #endif
> + atomic_t stable_page_users;
> };
>
> int bdi_init(struct backing_dev_info *bdi);
> @@ -307,6 +308,21 @@ long wait_iff_congested(struct zone *zone, int sync, long timeout);
> int pdflush_proc_obsolete(struct ctl_table *table, int write,
> void __user *buffer, size_t *lenp, loff_t *ppos);
>
> +static inline void bdi_require_stable_pages(struct backing_dev_info *bdi)
> +{
> + atomic_inc(&bdi->stable_page_users);
> +}
> +
> +static inline void bdi_unrequire_stable_pages(struct backing_dev_info *bdi)
> +{
> + atomic_dec(&bdi->stable_page_users);
> +}
> +
> +static inline bool bdi_cap_stable_pages_required(struct backing_dev_info *bdi)
> +{
> + return atomic_read(&bdi->stable_page_users) > 0;
> +}
> +
> static inline bool bdi_cap_writeback_dirty(struct backing_dev_info *bdi)
> {
> return !(bdi->capabilities & BDI_CAP_NO_WRITEBACK);
> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
> index 1756001..bf927c0 100644
> --- a/include/linux/blkdev.h
> +++ b/include/linux/blkdev.h
> @@ -458,6 +458,16 @@ struct request_queue {
> (1 << QUEUE_FLAG_SAME_COMP) | \
> (1 << QUEUE_FLAG_ADD_RANDOM))
>
> +static inline void queue_require_stable_pages(struct request_queue *q)
> +{
> + bdi_require_stable_pages(&q->backing_dev_info);
> +}
> +
> +static inline void queue_unrequire_stable_pages(struct request_queue *q)
> +{
> + bdi_unrequire_stable_pages(&q->backing_dev_info);
> +}
> +
> static inline void queue_lockdep_assert_held(struct request_queue *q)
> {
> if (q->queue_lock)
> diff --git a/mm/backing-dev.c b/mm/backing-dev.c
> index d3ca2b3..dd9f5ed 100644
> --- a/mm/backing-dev.c
> +++ b/mm/backing-dev.c
> @@ -221,12 +221,48 @@ static ssize_t max_ratio_store(struct device *dev,
> }
> BDI_SHOW(max_ratio, bdi->max_ratio)
>
> +static ssize_t stable_pages_required_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 spw;
> + ssize_t ret;
> +
> + ret = kstrtouint(buf, 10, &spw);
> + if (ret < 0)
> + return ret;
> +
> + /*
> + * SPW could be enabled due to hw requirement, so don't
> + * let users disable it.
> + */
> + if (bdi_cap_stable_pages_required(bdi) && spw == 0)
> + return -EINVAL;
> +
> + if (spw != 0)
> + atomic_inc(&bdi->stable_page_users);
> +
> + return count;
> +}
> +
> +static ssize_t stable_pages_required_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_cap_stable_pages_required(bdi) ? 1 : 0);
> +}
> +
> #define __ATTR_RW(attr) __ATTR(attr, 0644, attr##_show, attr##_store)
>
> static struct device_attribute bdi_dev_attrs[] = {
> __ATTR_RW(read_ahead_kb),
> __ATTR_RW(min_ratio),
> __ATTR_RW(max_ratio),
> + __ATTR_RW(stable_pages_required),
> __ATTR_NULL,
> };
>
> @@ -650,6 +686,8 @@ int bdi_init(struct backing_dev_info *bdi)
> bdi->write_bandwidth = INIT_BW;
> bdi->avg_write_bandwidth = INIT_BW;
>
> + atomic_set(&bdi->stable_page_users, 0);
> +
> err = fprop_local_init_percpu(&bdi->completions);
>
> if (err) {
>
--
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:[~2012-11-01 18:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 7:58 [RFC PATCH v2 0/3] mm/fs: Implement faster stable page writes on filesystems Darrick J. Wong
2012-11-01 7:58 ` [PATCH 1/3] bdi: Track users that require stable page writes Darrick J. Wong
2012-11-01 13:31 ` Jan Kara
2012-11-01 18:21 ` Boaz Harrosh [this message]
2012-11-01 18:57 ` Darrick J. Wong
2012-11-01 22:56 ` Boaz Harrosh
[not found] ` <5092FE22.30906-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2012-11-01 23:15 ` Jan Kara
2012-11-01 7:58 ` [PATCH 2/3] mm: Only enforce stable page writes if the backing device requires it Darrick J. Wong
[not found] ` <20121101075821.16153.38301.stgit-yuuUpGxbzT9UbpRmUfBrXUB+6BGkLq7r@public.gmane.org>
2012-11-01 13:28 ` Jan Kara
2012-11-01 7:58 ` [PATCH 3/3] fs: Fix remaining filesystems to wait for stable page writeback Darrick J. Wong
[not found] ` <20121101075829.16153.92036.stgit-yuuUpGxbzT9UbpRmUfBrXUB+6BGkLq7r@public.gmane.org>
2012-11-01 12:36 ` Jan Kara
2012-11-01 18:43 ` Boaz Harrosh
2012-11-01 20:22 ` Jeff Layton
2012-11-01 22:23 ` Boaz Harrosh
2012-11-01 22:47 ` Darrick J. Wong
2012-11-02 0:36 ` Jeff Layton
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=5092BDA2.6090001@panasas.com \
--to=bharrosh@panasas.com \
--cc=adrian.hunter@intel.com \
--cc=axboe@kernel.dk \
--cc=ceph-devel@vger.kernel.org \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=dedekind1@gmail.com \
--cc=dhowells@redhat.com \
--cc=ericvh@gmail.com \
--cc=jack@suse.cz \
--cc=jlbec@evilplan.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lucho@ionkov.net \
--cc=martin.petersen@oracle.com \
--cc=mfasheh@suse.com \
--cc=neilb@suse.de \
--cc=ocfs2-devel@oss.oracle.com \
--cc=rminnich@sandia.gov \
--cc=sage@inktank.com \
--cc=sfrench@samba.org \
--cc=tytso@mit.edu \
--cc=v9fs-developer@lists.sourceforge.net \
/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).