messages from 2025-05-01 13:43:06 to 2025-05-06 09:38:03 UTC [more...]
add more bio helpers v2
2025-05-06 9:37 UTC (26+ messages)
` [PATCH 03/19] block: add a bio_add_max_vecs helper
` [PATCH 04/19] block: add a bio_add_vmalloc helpers
` [PATCH 07/19] block: simplify bio_map_kern
` [PATCH 13/19] dm-bufio: use bio_add_virt_nofail
` [PATCH 14/19] dm-integrity: "
` [PATCH 15/19] xfs: simplify xfs_buf_submit_bio
` [PATCH 17/19] xfs: simplify building the bio in xlog_write_iclog
` [PATCH 19/19] hfsplus: use bdev_rw_virt in hfsplus_submit_bio
` 回复: "
[PATCH v12 00/17] large atomic writes for xfs
2025-05-06 9:04 UTC (18+ messages)
` [PATCH v12 01/17] fs: add atomic write unit max opt to statx
` [PATCH v12 02/17] xfs: only call xfs_setsize_buftarg once per buffer target
` [PATCH v12 03/17] xfs: rename xfs_inode_can_atomicwrite() -> xfs_inode_can_hw_atomic_write()
` [PATCH v12 04/17] xfs: separate out setting buftarg atomic writes limits
` [PATCH v12 05/17] xfs: add helpers to compute log item overhead
` [PATCH v12 06/17] xfs: add helpers to compute transaction reservation for finishing intent items
` [PATCH v12 07/17] xfs: ignore HW which cannot atomic write a single block
` [PATCH v12 08/17] xfs: allow block allocator to take an alignment hint
` [PATCH v12 09/17] xfs: refactor xfs_reflink_end_cow_extent()
` [PATCH v12 10/17] xfs: refine atomic write size check in xfs_file_write_iter()
` [PATCH v12 11/17] xfs: add xfs_atomic_write_cow_iomap_begin()
` [PATCH v12 12/17] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
` [PATCH v12 13/17] xfs: commit CoW-based atomic writes atomically
` [PATCH v12 14/17] xfs: add xfs_file_dio_write_atomic()
` [PATCH v12 15/17] xfs: add xfs_calc_atomic_write_unit_max()
` [PATCH v12 16/17] xfs: update atomic write limits
` [PATCH v12 17/17] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
[PATCH v3 0/2] common: Move exit related functions to common/exit
2025-05-06 8:49 UTC (10+ messages)
` [PATCH v3 1/2] common: Move exit related functions to a common/exit
` [PATCH v3 2/2] check: Replace exit with _fatal and _exit in check
[RFC PATCH v4 00/11] fallocate: introduce FALLOC_FL_WRITE_ZEROES flag
2025-05-06 7:51 UTC (21+ messages)
` [RFC PATCH v4 01/11] block: introduce BLK_FEAT_WRITE_ZEROES_UNMAP to queue limits features
` [RFC PATCH v4 02/11] nvme: set BLK_FEAT_WRITE_ZEROES_UNMAP if device supports DEAC bit
` [RFC PATCH v4 03/11] nvme-multipath: add BLK_FEAT_WRITE_ZEROES_UNMAP support
` [RFC PATCH v4 04/11] nvmet: set WZDS and DRB if device supports BLK_FEAT_WRITE_ZEROES_UNMAP
` [RFC PATCH v4 07/11] fs: statx add write zeroes unmap attribute
` [RFC PATCH v4 08/11] fs: introduce FALLOC_FL_WRITE_ZEROES to fallocate
[PATCH v11 00/16] large atomic writes for xfs
2025-05-06 6:57 UTC (35+ messages)
` [PATCH v11 01/16] fs: add atomic write unit max opt to statx
` [PATCH v11 02/16] xfs: only call xfs_setsize_buftarg once per buffer target
` [PATCH v11 03/16] xfs: add helpers to compute log item overhead
` [PATCH v11 04/16] xfs: add helpers to compute transaction reservation for finishing intent items
` [PATCH v11 05/16] xfs: rename xfs_inode_can_atomicwrite() -> xfs_inode_can_hw_atomic_write()
` [PATCH v11 06/16] xfs: ignore HW which cannot atomic write a single block
` [PATCH v11 07/16] xfs: allow block allocator to take an alignment hint
` [PATCH v11 08/16] xfs: refactor xfs_reflink_end_cow_extent()
` [PATCH v11 09/16] xfs: refine atomic write size check in xfs_file_write_iter()
` [PATCH v11 10/16] xfs: add xfs_atomic_write_cow_iomap_begin()
` [PATCH v11 11/16] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
` [PATCH v11 12/16] xfs: commit CoW-based atomic writes atomically
` [PATCH v11 13/16] xfs: add xfs_file_dio_write_atomic()
` [PATCH v11 14/16] xfs: add xfs_calc_atomic_write_unit_max()
` [PATCH v11 15/16] xfs: update atomic write limits
` [PATCH v11 16/16] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
[PATCH] xfs: free up mp->m_free[0].count in error case
2025-05-06 4:58 UTC (3+ messages)
Question: Is it possible to recover deleted files from a healthy XFS filesystem?
2025-05-06 4:34 UTC (5+ messages)
[PATCH] xfs: Remove deprecated xfs_bufd sysctl parameters
2025-05-06 1:15 UTC
Sequential read from NVMe/XFS twice slower on Fedora 42 than on Rocky 9.5
2025-05-05 22:56 UTC (8+ messages)
[PATCH v2] xfs: Verify DA node btree hash order
2025-05-05 22:17 UTC (2+ messages)
new tests for zoned xfs
2025-05-05 15:08 UTC (18+ messages)
` [PATCH 04/15] xfs: add a test to check that data growfs fails with internal rt device
` [PATCH 05/15] add a new rw_hint helper
` [PATCH 06/15] xfs: add a test for write lifetime hints
` [PATCH 07/15] xfs: add a test for writeback after close
` [PATCH 08/15] xfs: test zone stream separation for two direct writers
` [PATCH 09/15] xfs: test zone stream separation for two buffered writers
` [PATCH 10/15] xfs: test zoned ENOSPC behavior with multiple writers
` [PATCH 11/15] xfs: test zoned GC file defragmentation for sequential writers
` [PATCH 12/15] xfs: test zoned GC file defragmentation for random writers
` [PATCH 13/15] xfs: test that xfs_repair does not mess up the zone used counter
` [PATCH 14/15] xfs: test that truncate does not spuriously return ENOSPC
` [PATCH 15/15] xfs: test that we can handle spurious zone wp advancements
` [PATCH v2 "
[PATCH] xfs: don't assume perags are initialised when trimming AGs
2025-05-05 15:07 UTC (6+ messages)
[RFC PATCH 0/2] Add mru cache for inode to zone allocation mapping
2025-05-05 15:07 UTC (9+ messages)
` [RFC PATCH 1/2] xfs: free the item in xfs_mru_cache_insert on failure
` [RFC PATCH 2/2] xfs: add inode to zone caching for data placement
[PATCH v5] generic: add a test for atomic writes
2025-05-05 14:57 UTC (5+ messages)
[PATCH 0/6] iomap: misc buffered write path cleanups and prep
2025-05-05 14:39 UTC (22+ messages)
` [PATCH 1/6] iomap: resample iter->pos after iomap_write_begin() calls
` [PATCH 2/6] iomap: drop unnecessary pos param from iomap_write_[begin|end]
` [PATCH 3/6] iomap: drop pos param from __iomap_[get|put]_folio()
` [PATCH 4/6] iomap: helper to trim pos/bytes to within folio
` [PATCH 5/6] iomap: push non-large folio check into get folio path
` [PATCH 6/6] iomap: rework iomap_write_begin() to return folio offset and length
[PATCH] xfs: fix diff_two_keys calculation for cnt btree
2025-05-05 10:47 UTC (3+ messages)
[PATCH] ext4/002: make generic to support xfs
2025-05-05 9:20 UTC (3+ messages)
[ANNOUNCE] xfs-linux: next-rc updated to 23be716b1c4f
2025-05-05 8:22 UTC
[PATCH] xfs: Verify DA node btree hash order
2025-05-05 7:10 UTC (6+ messages)
[PATCH v10 00/15] large atomic writes for xfs
2025-05-05 5:22 UTC (24+ messages)
` [PATCH v10 01/15] fs: add atomic write unit max opt to statx
` [PATCH v10.1 1.1/15] xfs: only call xfs_setsize_buftarg once per buffer target
` [PATCH v10 02/15] xfs: add helpers to compute log item overhead
` [PATCH v10 03/15] xfs: add helpers to compute transaction reservation for finishing intent items
` [PATCH v10 04/15] xfs: rename xfs_inode_can_atomicwrite() -> xfs_inode_can_hw_atomic_write()
` [PATCH v10 05/15] xfs: ignore HW which cannot atomic write a single block
` [PATCH v10.1 "
` [PATCH v10 06/15] xfs: allow block allocator to take an alignment hint
` [PATCH v10 07/15] xfs: refactor xfs_reflink_end_cow_extent()
` [PATCH v10 08/15] xfs: refine atomic write size check in xfs_file_write_iter()
` [PATCH v10 09/15] xfs: add xfs_atomic_write_cow_iomap_begin()
` [PATCH v10 10/15] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
` [PATCH v10 11/15] xfs: commit CoW-based atomic writes atomically
` [PATCH v10 12/15] xfs: add xfs_file_dio_write_atomic()
` [PATCH v10 13/15] xfs: add xfs_calc_atomic_write_unit_max()
` [PATCH v10 14/15] xfs: update atomic write limits
` [PATCH v10 15/15] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
` [PATCH 16/15] xfs: only call xfs_setsize_buftarg once per buffer target
` [PATCH 17/15] xfs: move buftarg atomic write geometry config to setsize_buftarg
XFS complains about data corruption after xfs_repair
2025-05-03 22:34 UTC (2+ messages)
[PATCH v5 0/9] xfs/iomap: fix non-atomic clone operation and don't update size when zeroing range post eof
2025-05-02 14:38 UTC (4+ messages)
` [PATCH v5 4/9] xfs: convert delayed extents to unwritten when zeroing post eof blocks
[PATCH 0/2] add read-only logdev/rtdev mount-remount tests
2025-05-02 11:40 UTC (8+ messages)
` [PATCH 2/2] xfs: add mount test for read only log devices
[PATCH v2] xfs: allow ro mounts if rtdev or logdev are read-only
2025-05-02 8:47 UTC (2+ messages)
[PATCH v7 0/2] mkfs: add ability to populate filesystem from directory
2025-05-02 7:04 UTC (5+ messages)
` [PATCH v7 1/2] proto: add ability to populate a filesystem from a directory
[PATCH v3 0/1] xfs: Fail remount with noattr2 on a v5 xfs with v4 enabled kernel
2025-05-02 7:01 UTC (3+ messages)
` [PATCH v3 1/1] xfs: Fail remount with noattr2 on a v5 with v4 enabled
[RFC PATCH 0/2] Implement concurrent buffered write with folio lock
2025-05-01 23:57 UTC (5+ messages)
[PATCH v8 0/2] mkfs: add ability to populate filesystem from directory
2025-05-01 22:18 UTC (5+ messages)
` [PATCH v8 1/2] proto: add ability to populate a filesystem from a directory
` [PATCH v8 2/2] mkfs: modify -p flag "
[PATCH v9 00/15] large atomic writes for xfs
2025-05-01 19:53 UTC (14+ messages)
` [PATCH v9 05/15] xfs: ignore HW which cannot atomic write a single block
` [PATCH v9 13/15] xfs: add xfs_compute_atomic_write_unit_max()
finishe xfstests support for zoned XFS
2025-05-01 15:02 UTC (2+ messages)
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox