All of lore.kernel.org
 help / color / mirror / Atom feed
From: hui.zhu@linux.dev
To: "SeongJae Park" <sj@kernel.org>
Cc: "SeongJae Park" <sj@kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Muchun Song" <muchun.song@linux.dev>,
	"Oscar Salvador" <osalvador@suse.de>,
	"David Hildenbrand" <david@redhat.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	"Hui Zhu" <zhuhui@kylinos.cn>
Subject: Re: [PATCH 0/2] mm/hugetlb: refactor sysfs/sysctl interfaces
Date: Tue, 04 Nov 2025 08:39:44 +0000	[thread overview]
Message-ID: <f4a25c9dc3af7365b6ade4cd9a0404530afeaa11@linux.dev> (raw)
In-Reply-To: <20251104044355.94885-1-sj@kernel.org>

2025年11月4日 12:43, "SeongJae Park" <sj@kernel.org mailto:sj@kernel.org?to=%22SeongJae%20Park%22%20%3Csj%40kernel.org%3E > 写到:


> 
> On Mon, 3 Nov 2025 16:22:07 +0800 Hui Zhu <hui.zhu@linux.dev> wrote:
> 
> > 
> > From: Hui Zhu <zhuhui@kylinos.cn>
> >  
> >  The hugetlb.c file has grown significantly and become difficult to
> >  maintain. This patch series extracts the sysfs and sysctl interface
> >  code into separate dedicated files to improve code organization.
> >  
> >  The refactoring includes:
> >  - Patch 1: Extract sysfs interface into mm/hugetlb_sysfs.c
> >  - Patch 2: Extract sysctl interface into mm/hugetlb_sysctl.c
> >  
> >  No functional changes are introduced in this series. The code is moved
> >  as-is, with only minor formatting adjustments for code style
> >  consistency. This should make future maintenance and enhancements to
> >  the hugetlb subsystem easier.
> >  
> >  Testing: The patch series has been compile-tested and maintains the
> >  same functionality as the original code.
> >  
> >  Geliang Tang (1):
> >  mm/hugetlb: extract sysfs into hugetlb_sysfs.c
> >  
> >  Hui Zhu (1):
> >  mm/hugetlb: extract sysctl into hugetlb_sysctl.c
> >  
> >  mm/Makefile | 2 +-
> >  mm/hugetlb.c | 852 +-----------------------------------------
> >  mm/hugetlb_internal.h | 116 ++++++
> >  mm/hugetlb_sysctl.c | 136 +++++++
> >  mm/hugetlb_sysfs.c | 632 +++++++++++++++++++++++++++++++
> >  5 files changed, 894 insertions(+), 844 deletions(-)
> >  create mode 100644 mm/hugetlb_internal.h
> >  create mode 100644 mm/hugetlb_sysctl.c
> >  create mode 100644 mm/hugetlb_sysfs.c
> > 
> I think MAINTAINERS file should also be updated for the newly added files.
> 

Updated MAINTAINERS to v3 version according your comments.

Best,
Hui

> Thanks,
> SJ
> 
> [...]
>


      reply	other threads:[~2025-11-04  8:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03  8:22 [PATCH 0/2] mm/hugetlb: refactor sysfs/sysctl interfaces Hui Zhu
2025-11-03  8:22 ` [PATCH 1/2] mm/hugetlb: extract sysfs into hugetlb_sysfs.c Hui Zhu
2025-11-03 16:28   ` David Hildenbrand (Red Hat)
2025-11-04  2:41     ` hui.zhu
2025-11-04  9:05       ` David Hildenbrand (Red Hat)
2025-11-03  8:22 ` [PATCH 2/2] mm/hugetlb: extract sysctl into hugetlb_sysctl.c Hui Zhu
2025-11-04  4:43 ` [PATCH 0/2] mm/hugetlb: refactor sysfs/sysctl interfaces SeongJae Park
2025-11-04  8:39   ` hui.zhu [this message]

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=f4a25c9dc3af7365b6ade4cd9a0404530afeaa11@linux.dev \
    --to=hui.zhu@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    --cc=sj@kernel.org \
    --cc=zhuhui@kylinos.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.