From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 214009] Compression has no real effect in disk usage
Date: Mon, 09 Aug 2021 14:35:46 +0000 [thread overview]
Message-ID: <bug-214009-202145-ck9xvsVUic@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214009-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214009
Chao Yu (chao@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |chao@kernel.org
--- Comment #1 from Chao Yu (chao@kernel.org) ---
Could you please check below documentation?
https://elixir.bootlin.com/linux/latest/source/Documentation/filesystems/f2fs.rst#L824
We've added three ioctl interfaces to query/release/reserve saved block of
compressed file:
- F2FS_IOC_GET_COMPRESS_BLOCKS
- F2FS_IOC_RELEASE_COMPRESS_BLOCKS
- F2FS_IOC_RESERVE_COMPRESS_BLOCKS
f2fs_io command has supported these ioctls with below sub-command:
get_cblocks get number of reserved blocks on compress inode
release_cblocks release reserved blocks on compress inode
reserve_cblocks reserve blocks on compress inode
You can use ioctls directly in your apps, or use f2fs_io in the script to
operate the space compression saved, let me know if you have further question.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-08-09 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 14:08 [f2fs-dev] [Bug 214009] New: Compression has no real effect in disk usage bugzilla-daemon
2021-08-09 14:35 ` bugzilla-daemon [this message]
2021-08-09 14:41 ` [f2fs-dev] [Bug 214009] " bugzilla-daemon
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=bug-214009-202145-ck9xvsVUic@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.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).