linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Kaixiong Yu <yukaixiong@huawei.com>
Cc: akpm@linux-foundation.org, mcgrof@kernel.org,
	ysato@users.sourceforge.jp, dalias@libc.org,
	glaubitz@physik.fu-berlin.de, luto@kernel.org,
	tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, hpa@zytor.com,
	viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
	kees@kernel.org, j.granados@samsung.com, willy@infradead.org,
	Liam.Howlett@oracle.com, vbabka@suse.cz,
	lorenzo.stoakes@oracle.com, trondmy@kernel.org, anna@kernel.org,
	chuck.lever@oracle.com, jlayton@kernel.org, neilb@suse.de,
	okorniev@redhat.com, Dai.Ngo@oracle.com, tom@talpey.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, paul@paul-moore.com, jmorris@namei.org,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-nfs@vger.kernel.org, netdev@vger.kernel.org,
	linux-security-module@vger.kernel.org, dhowells@redhat.com,
	haifeng.xu@shopee.com, baolin.wang@linux.alibaba.com,
	shikemeng@huaweicloud.com, dchinner@redhat.com,
	bfoster@redhat.com, souravpanda@google.com, hannes@cmpxchg.org,
	rientjes@google.com, pasha.tatashin@soleen.com, david@redhat.com,
	ryan.roberts@arm.com, ying.huang@intel.com,
	yang@os.amperecomputing.com, zev@bewilderbeest.net,
	serge@hallyn.com, vegard.nossum@oracle.com,
	wangkefeng.wang@huawei.com, sunnanyong@huawei.com
Subject: Re: [PATCH v3 -next 09/15] fs: fs-writeback: move sysctl to fs/fs-writeback.c
Date: Mon, 14 Oct 2024 14:14:27 +0200	[thread overview]
Message-ID: <20241014121427.vuebknsmdlrtbveh@quack3> (raw)
In-Reply-To: <20241010152215.3025842-10-yukaixiong@huawei.com>

On Thu 10-10-24 23:22:09, Kaixiong Yu wrote:
> The dirtytime_expire_interval belongs to fs/fs-writeback.c, move it to
> fs/fs-writeback.c from /kernel/sysctl.c. And remove the useless extern
> variable declaration and the function declaration from
> include/linux/writeback.h
> 
> Signed-off-by: Kaixiong Yu <yukaixiong@huawei.com>
> Reviewed-by: Kees Cook <kees@kernel.org>

Looks good. Feel free to add:

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

								Honza

> ---
> v3:
>  - change dirtytime_expire_interval to static type
>  - change the title
> ---
>  fs/fs-writeback.c         | 30 +++++++++++++++++++++---------
>  include/linux/writeback.h |  4 ----
>  kernel/sysctl.c           |  8 --------
>  3 files changed, 21 insertions(+), 21 deletions(-)
> 
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index d8bec3c1bb1f..4fedefdb8e15 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -65,7 +65,7 @@ struct wb_writeback_work {
>   * timestamps written to disk after 12 hours, but in the worst case a
>   * few inodes might not their timestamps updated for 24 hours.
>   */
> -unsigned int dirtytime_expire_interval = 12 * 60 * 60;
> +static unsigned int dirtytime_expire_interval = 12 * 60 * 60;
>  
>  static inline struct inode *wb_inode(struct list_head *head)
>  {
> @@ -2413,14 +2413,7 @@ static void wakeup_dirtytime_writeback(struct work_struct *w)
>  	schedule_delayed_work(&dirtytime_work, dirtytime_expire_interval * HZ);
>  }
>  
> -static int __init start_dirtytime_writeback(void)
> -{
> -	schedule_delayed_work(&dirtytime_work, dirtytime_expire_interval * HZ);
> -	return 0;
> -}
> -__initcall(start_dirtytime_writeback);
> -
> -int dirtytime_interval_handler(const struct ctl_table *table, int write,
> +static int dirtytime_interval_handler(const struct ctl_table *table, int write,
>  			       void *buffer, size_t *lenp, loff_t *ppos)
>  {
>  	int ret;
> @@ -2431,6 +2424,25 @@ int dirtytime_interval_handler(const struct ctl_table *table, int write,
>  	return ret;
>  }
>  
> +static struct ctl_table vm_fs_writeback_table[] = {
> +	{
> +		.procname	= "dirtytime_expire_seconds",
> +		.data		= &dirtytime_expire_interval,
> +		.maxlen		= sizeof(dirtytime_expire_interval),
> +		.mode		= 0644,
> +		.proc_handler	= dirtytime_interval_handler,
> +		.extra1		= SYSCTL_ZERO,
> +	},
> +};
> +
> +static int __init start_dirtytime_writeback(void)
> +{
> +	schedule_delayed_work(&dirtytime_work, dirtytime_expire_interval * HZ);
> +	register_sysctl_init("vm", vm_fs_writeback_table);
> +	return 0;
> +}
> +__initcall(start_dirtytime_writeback);
> +
>  /**
>   * __mark_inode_dirty -	internal function to mark an inode dirty
>   *
> diff --git a/include/linux/writeback.h b/include/linux/writeback.h
> index d6db822e4bb3..5f35b24aff7b 100644
> --- a/include/linux/writeback.h
> +++ b/include/linux/writeback.h
> @@ -351,12 +351,8 @@ extern struct wb_domain global_wb_domain;
>  /* These are exported to sysctl. */
>  extern unsigned int dirty_writeback_interval;
>  extern unsigned int dirty_expire_interval;
> -extern unsigned int dirtytime_expire_interval;
>  extern int laptop_mode;
>  
> -int dirtytime_interval_handler(const struct ctl_table *table, int write,
> -		void *buffer, size_t *lenp, loff_t *ppos);
> -
>  void global_dirty_limits(unsigned long *pbackground, unsigned long *pdirty);
>  unsigned long wb_calc_thresh(struct bdi_writeback *wb, unsigned long thresh);
>  unsigned long cgwb_calc_thresh(struct bdi_writeback *wb);
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index d3de31ec74bf..373e018b950c 100644
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@ -2024,14 +2024,6 @@ static struct ctl_table kern_table[] = {
>  };
>  
>  static struct ctl_table vm_table[] = {
> -	{
> -		.procname	= "dirtytime_expire_seconds",
> -		.data		= &dirtytime_expire_interval,
> -		.maxlen		= sizeof(dirtytime_expire_interval),
> -		.mode		= 0644,
> -		.proc_handler	= dirtytime_interval_handler,
> -		.extra1		= SYSCTL_ZERO,
> -	},
>  	{
>  		.procname	= "drop_caches",
>  		.data		= &sysctl_drop_caches,
> -- 
> 2.34.1
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR


  reply	other threads:[~2024-10-14 12:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20241010141133eucas1p1999f17c74198d3880cbd345276bcd3bd@eucas1p1.samsung.com>
2024-10-10 15:22 ` [PATCH v3 -next 00/15] sysctl: move sysctls from vm_table into its own files Kaixiong Yu
2024-10-10 15:22   ` [PATCH v3 -next 01/15] mm: vmstat: move sysctls to mm/vmstat.c Kaixiong Yu
2024-10-10 15:22   ` [PATCH v3 -next 02/15] mm: filemap: move sysctl to mm/filemap.c Kaixiong Yu
2024-10-10 15:22   ` [PATCH v3 -next 03/15] mm: swap: move sysctl to mm/swap.c Kaixiong Yu
2024-10-10 15:22   ` [PATCH v3 -next 04/15] mm: vmscan: move vmscan sysctls to mm/vmscan.c Kaixiong Yu
2024-10-10 15:22   ` [PATCH v3 -next 05/15] mm: util: move sysctls to mm/util.c Kaixiong Yu
2024-10-10 15:22   ` [PATCH v3 -next 06/15] mm: mmap: move sysctl to mm/mmap.c Kaixiong Yu
2024-10-10 15:22   ` [PATCH v3 -next 07/15] security: min_addr: move sysctl to security/min_addr.c Kaixiong Yu
2024-10-10 15:22   ` [PATCH v3 -next 08/15] mm: nommu: move sysctl to mm/nommu.c Kaixiong Yu
2024-10-10 15:22   ` [PATCH v3 -next 09/15] fs: fs-writeback: move sysctl to fs/fs-writeback.c Kaixiong Yu
2024-10-14 12:14     ` Jan Kara [this message]
2024-10-10 15:22   ` [PATCH v3 -next 10/15] fs: drop_caches: move sysctl to fs/drop_caches.c Kaixiong Yu
2024-10-14 12:15     ` Jan Kara
2024-10-15 14:02     ` Christian Brauner
2024-10-10 15:22   ` [PATCH v3 -next 11/15] sunrpc: use vfs_pressure_ratio() helper Kaixiong Yu
2024-10-10 14:44     ` Jeff Layton
2024-10-10 21:43       ` NeilBrown
2024-10-11 12:38         ` Jeff Layton
2024-12-19 10:20           ` yukaixiong
2024-12-19 10:17         ` yukaixiong
2024-10-10 15:22   ` [PATCH v3 -next 12/15] fs: dcache: move the sysctl to fs/dcache.c Kaixiong Yu
2024-10-10 15:22   ` [PATCH v3 -next 13/15] x86: vdso: move the sysctl to arch/x86/entry/vdso/vdso32-setup.c Kaixiong Yu
2024-10-10 15:22   ` [PATCH v3 -next 14/15] sh: vdso: move the sysctl to arch/sh/kernel/vsyscall/vsyscall.c Kaixiong Yu
2024-10-10 15:22   ` [PATCH v3 -next 15/15] sysctl: remove unneeded include Kaixiong Yu
2024-10-11 13:04   ` [PATCH v3 -next 00/15] sysctl: move sysctls from vm_table into its own files Liam R. Howlett
2024-10-14  1:33     ` yukaixiong
2024-10-21  7:22   ` Joel Granados
2024-10-24  8:07     ` yukaixiong
2024-10-24  8:59       ` Joel Granados
2024-12-19 11:15         ` yukaixiong

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=20241014121427.vuebknsmdlrtbveh@quack3 \
    --to=jack@suse.cz \
    --cc=Dai.Ngo@oracle.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=anna@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=bfoster@redhat.com \
    --cc=bp@alien8.de \
    --cc=brauner@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=dalias@libc.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=david@redhat.com \
    --cc=dchinner@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=haifeng.xu@shopee.com \
    --cc=hannes@cmpxchg.org \
    --cc=hpa@zytor.com \
    --cc=j.granados@samsung.com \
    --cc=jlayton@kernel.org \
    --cc=jmorris@namei.org \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=luto@kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mingo@redhat.com \
    --cc=neilb@suse.de \
    --cc=netdev@vger.kernel.org \
    --cc=okorniev@redhat.com \
    --cc=pabeni@redhat.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=paul@paul-moore.com \
    --cc=rientjes@google.com \
    --cc=ryan.roberts@arm.com \
    --cc=serge@hallyn.com \
    --cc=shikemeng@huaweicloud.com \
    --cc=souravpanda@google.com \
    --cc=sunnanyong@huawei.com \
    --cc=tglx@linutronix.de \
    --cc=tom@talpey.com \
    --cc=trondmy@kernel.org \
    --cc=vbabka@suse.cz \
    --cc=vegard.nossum@oracle.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wangkefeng.wang@huawei.com \
    --cc=willy@infradead.org \
    --cc=yang@os.amperecomputing.com \
    --cc=ying.huang@intel.com \
    --cc=ysato@users.sourceforge.jp \
    --cc=yukaixiong@huawei.com \
    --cc=zev@bewilderbeest.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).