From: Jan Kara <jack@suse.cz>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: axboe@kernel.dk, dhowells@redhat.com, vbabka@suse.cz,
willy@infradead.org, akpm@linux-foundation.org,
zhanglianjie@uniontech.com, neilb@suse.de, jack@suse.cz,
bvanassche@acm.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] writeback: remove unused macro DIRTY_FULL_SCOPE
Date: Fri, 9 Sep 2022 11:36:34 +0200 [thread overview]
Message-ID: <20220909093634.od4aukp2oumgflcc@quack3> (raw)
In-Reply-To: <20220909025711.32012-1-linmiaohe@huawei.com>
On Fri 09-09-22 10:57:11, Miaohe Lin wrote:
> It's introduced but never used. Remove it.
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
Looks good. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> include/linux/writeback.h | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/include/linux/writeback.h b/include/linux/writeback.h
> index 3f045f6d6c4f..06f9291b6fd5 100644
> --- a/include/linux/writeback.h
> +++ b/include/linux/writeback.h
> @@ -17,20 +17,12 @@ struct bio;
> DECLARE_PER_CPU(int, dirty_throttle_leaks);
>
> /*
> - * The 1/4 region under the global dirty thresh is for smooth dirty throttling:
> - *
> - * (thresh - thresh/DIRTY_FULL_SCOPE, thresh)
> - *
> - * Further beyond, all dirtier tasks will enter a loop waiting (possibly long
> - * time) for the dirty pages to drop, unless written enough pages.
> - *
> * The global dirty threshold is normally equal to the global dirty limit,
> * except when the system suddenly allocates a lot of anonymous memory and
> * knocks down the global dirty threshold quickly, in which case the global
> * dirty limit will follow down slowly to prevent livelocking all dirtier tasks.
> */
> #define DIRTY_SCOPE 8
> -#define DIRTY_FULL_SCOPE (DIRTY_SCOPE / 2)
>
> struct backing_dev_info;
>
> --
> 2.23.0
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2022-09-09 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 2:57 Miaohe Lin
2022-09-09 9:36 ` Jan Kara [this message]
2022-09-10 11:37 ` Jens Axboe
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=20220909093634.od4aukp2oumgflcc@quack3 \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dhowells@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=zhanglianjie@uniontech.com \
/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
all inboxes | Powered by JetHome®