From: Gao Xiang <hsiangkao@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Miao Xie <miaoxie@huawei.com>, Chao Yu <yuchao0@huawei.com>,
Fang Wei <fangwei1@huawei.com>,
Li Guifu <bluce.liguifu@huawei.com>,
Gao Xiang <hsiangkao@redhat.com>
Subject: [GIT PULL] erofs update for 5.11-rc1
Date: Tue, 15 Dec 2020 18:08:55 +0800 [thread overview]
Message-ID: <20201215100855.GA581189@xiangao.remote.csb> (raw)
Hi Linus,
Could you consider this pull request for 5.11-rc1?
This cycle we'd like to get rid of magical page->mapping type marks
for temporary pages which had some concern before, now such usage
is replaced with specific page->private. Also switch to inplace I/O
instead of allocating extra cached pages to avoid direct reclaim
under low memory scenario. There are some bmap bugfix and minor
cleanups as well.
All commits have been tested and have been in linux-next for a while.
This merges cleanly with master.
[ Additionally, there is another lz4 inplace decompression fix [1] due
to some different overlapped memcpy() implementation which was reviewed
and added to akpm tree, hopefully upstream for this 5.11 cycle too. ]
Thanks,
Gao Xiang
[1] https://lore.kernel.org/r/20201122030749.2698994-1-hsiangkao@redhat.com
The following changes since commit 0477e92881850d44910a7e94fc2c46f96faa131f:
Linux 5.10-rc7 (2020-12-06 14:25:12 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-5.11-rc1
for you to fetch changes up to d8b3df8b1048405e73558b88cba2adf29490d468:
erofs: avoid using generic_block_bmap (2020-12-10 11:07:40 +0800)
----------------------------------------------------------------
Changes since last update:
- get rid of magical page->mapping type marks;
- switch to inplace I/O under low memory scenario;
- return the correct block number for bmap();
- some minor cleanups.
----------------------------------------------------------------
Gao Xiang (4):
erofs: get rid of magical Z_EROFS_MAPPING_STAGING
erofs: insert to managed cache after adding to pcl
erofs: simplify try_to_claim_pcluster()
erofs: force inplace I/O under low memory scenario
Huang Jianan (1):
erofs: avoid using generic_block_bmap
Vladimir Zapolskiy (1):
erofs: remove a void EROFS_VERSION macro set in Makefile
fs/erofs/Makefile | 5 --
fs/erofs/compress.h | 54 +++++++++++----
fs/erofs/data.c | 26 ++------
fs/erofs/decompressor.c | 2 +-
fs/erofs/zdata.c | 172 ++++++++++++++++++++++++++++--------------------
fs/erofs/zdata.h | 1 +
6 files changed, 149 insertions(+), 111 deletions(-)
next reply other threads:[~2020-12-15 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 10:08 Gao Xiang [this message]
2020-12-16 3:44 ` pr-tracker-bot
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=20201215100855.GA581189@xiangao.remote.csb \
--to=hsiangkao@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bluce.liguifu@huawei.com \
--cc=fangwei1@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yuchao0@huawei.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®