btrfs: allow creating inline data extents for sector size < page size case
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | btrfs: fix the qgroup data free range for inline data extentsfs/ | +1 | 0 replies | |
| 2/2 | btrfs: allow inline data extents creation if sector size < page sizefs/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] btrfs: allow creating inline data extents for sector size < page size case
There are two features disabled when sector size < page size (subpage) is allowed for btrfs:
- Inline data extent creation
- Sector perfect compressed write
Both share one critical technical problem, that inline or async submission all unlock the whole page.
Thankfully the major technical blockage is already solved with the recent sector perfect compressed write support for subpage cases.
So there is no need to disable inline data extent creation either. Yes, there are cases we can mixing inline and regular data extents, but that's also the case when page size == sector size, so it's not a show stopper.
The first patch is to fix a harmless bug that is only affecting subpage cases.
The second one enables the inline data extent creation for subpage cases.
Qu Wenruo (2):
btrfs: fix the qgroup data free range for inline data extents
btrfs: allow inline data extents creation if sector size < page size
fs/btrfs/inode.c | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-)
Signature · 1 line
2.47.0