btrfs: drop no longer needed atomic allocation for tree mod log operations
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest2 patches 1 replyIn review
- v12 patches 3 repliesSuperseded
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | btrfs: switch GFP_ATOMIC to GFP_NOFS when fixing up low keysfs/ | +1 | 0 replies | |
| 2/2 | btrfs: remove gfp_t flag from btrfs_tree_mod_log_insert_key()fs/ fs/ fs/ | +18 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/2] btrfs: drop no longer needed atomic allocation for tree mod log operations
From: Filipe Manana <[email protected]>
We are still doing an atomic memory allocation for tree mod log operations which is not needed anymore after we switch extent buffer locks to rw semaphores. This replaces that atomic allocation with a GFP_NOFS one, and then removes redundant gfp_t argument for btrfs_tree_mod_log_insert_key().
V2: Updated patch 2/2 to also remove the allocation flag from
alloc_tree_mod_elem().
Filipe Manana (2):
btrfs: switch GFP_ATOMIC to GFP_NOFS when fixing up low keys
btrfs: remove gfp_t flag from btrfs_tree_mod_log_insert_key()
fs/btrfs/ctree.c | 16 ++++++++-------- fs/btrfs/tree-mod-log.c | 19 +++++++++---------- fs/btrfs/tree-mod-log.h | 2 +- 3 files changed, 18 insertions(+), 19 deletions(-)
Signature · 1 line
2.35.1