mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/8] nilfs2: assorted cleanups
Date: Tue, 27 Aug 2024 02:41:08 +0900	[thread overview]
Message-ID: <20240826174116.5008-1-konishi.ryusuke@gmail.com> (raw)

Hi Andrew,

please add this series to the queue for the next cycle.

This is a collection of cleanup patches, with only the last three
focused on the log writer thread, the rest are miscellaneous.

Patches 1/8, 4/8, and 7/8 adopt common implementations, 2/8 uses a
generic macro, 5/8 removes dead code, 6/8 removes an unnecessary
reference, and 3/8 and 8/8 each simplify a paticular messy
implementation.

Thanks,
Ryusuke Konishi

Huang Xiaojia (1):
  nilfs2: use common implementation of file type

Ryusuke Konishi (7):
  nilfs2: use the BITS_PER_LONG macro
  nilfs2: separate inode type information from i_state field
  nilfs2: eliminate the shared counter and spinlock for i_generation
  nilfs2: do not repair reserved inode bitmap in nilfs_new_inode()
  nilfs2: remove sc_timer_task
  nilfs2: use kthread_create and kthread_stop for the log writer thread
  nilfs2: refactor nilfs_segctor_thread()

 fs/nilfs2/bmap.h      |   5 +-
 fs/nilfs2/dir.c       |  44 ++---------
 fs/nilfs2/inode.c     |  75 ++++---------------
 fs/nilfs2/nilfs.h     |  15 +++-
 fs/nilfs2/segment.c   | 170 ++++++++++++++++++------------------------
 fs/nilfs2/segment.h   |   5 --
 fs/nilfs2/super.c     |   1 +
 fs/nilfs2/the_nilfs.c |   5 --
 fs/nilfs2/the_nilfs.h |   6 --
 9 files changed, 108 insertions(+), 218 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-08-26 17:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26 17:41 Ryusuke Konishi [this message]
2024-08-26 17:41 ` [PATCH 1/8] nilfs2: use common implementation of file type Ryusuke Konishi
2024-08-26 17:41 ` [PATCH 2/8] nilfs2: use the BITS_PER_LONG macro Ryusuke Konishi
2024-08-26 17:41 ` [PATCH 3/8] nilfs2: separate inode type information from i_state field Ryusuke Konishi
2024-08-26 17:41 ` [PATCH 4/8] nilfs2: eliminate the shared counter and spinlock for i_generation Ryusuke Konishi
2024-08-26 17:41 ` [PATCH 5/8] nilfs2: do not repair reserved inode bitmap in nilfs_new_inode() Ryusuke Konishi
2024-08-26 17:41 ` [PATCH 6/8] nilfs2: remove sc_timer_task Ryusuke Konishi
2024-08-26 17:41 ` [PATCH 7/8] nilfs2: use kthread_create and kthread_stop for the log writer thread Ryusuke Konishi
2024-08-26 17:41 ` [PATCH 8/8] nilfs2: refactor nilfs_segctor_thread() Ryusuke Konishi

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=20240826174116.5008-1-konishi.ryusuke@gmail.com \
    --to=konishi.ryusuke@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    /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®