Linux-f2fs-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yongpeng Yang <yangyongpeng.storage@gmail.com>
To: Chao Yu <chao@kernel.org>,
	Yongpeng Yang <yangyongpeng.storage@gmail.com>,
	Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Yongpeng Yang <yangyongpeng@xiaomi.com>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [RFC PATCH v3 1/3] f2fs: introduce inline extent mapping for inode data blocks
Date: Thu, 6 Aug 2026 21:22:56 +0800	[thread overview]
Message-ID: <cec45733-552c-4bbc-b133-fd090e629900@gmail.com> (raw)
In-Reply-To: <022b437d-b1c9-4f62-aefc-a6d32ee6dbe3@kernel.org>

On 7/29/26 20:19, Chao Yu via Linux-f2fs-devel wrote:
> On 7/24/26 20:58, Yongpeng Yang wrote:
>>  fs/f2fs/Kconfig         |  18 +
>>  fs/f2fs/Makefile        |   1 +
>>  fs/f2fs/data.c          | 148 ++++++++-
>>  fs/f2fs/dir.c           |   1 +
>>  fs/f2fs/f2fs.h          |  44 ++-
>>  fs/f2fs/file.c          |   1 +
>>  fs/f2fs/iextent.c       | 712 ++++++++++++++++++++++++++++++++++++++++
>>  fs/f2fs/iextent.h       | 163 +++++++++
> 
> Hmmm, the code size is still a problem, too complicated to support all
> insertion, deletion, merging and splitting operations on inline extents.

I simplify inline extent update implementation in v4. Please review this
series:

https://lore.kernel.org/all/20260806131906.2961409-2-yangyongpeng.storage@gmail.com/

Thanks,
Yongpeng
> 
> Thanks,
> 
> 
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2026-08-06 13:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 12:58 [f2fs-dev] [RFC PATCH v3 0/3] f2fs: introduce inline extent mapping for inode data blocks Yongpeng Yang
2026-07-24 12:58 ` [f2fs-dev] [RFC PATCH v3 1/3] " Yongpeng Yang
2026-07-29 12:19   ` Chao Yu via Linux-f2fs-devel
2026-08-06 13:22     ` Yongpeng Yang [this message]
2026-07-24 12:58 ` [f2fs-dev] [RFC PATCH v3 2/3] f2fs: add sysfs interface for inline extent management Yongpeng Yang
2026-07-24 12:58 ` [f2fs-dev] [RFC PATCH v3 3/3] f2fs: introduce tracepoints for inline extent lookup and update Yongpeng Yang

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=cec45733-552c-4bbc-b133-fd090e629900@gmail.com \
    --to=yangyongpeng.storage@gmail.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=yangyongpeng@xiaomi.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