diff options
| author | Kent Overstreet <kent.overstreet@linux.dev> | 2024-10-19 18:27:09 -0400 |
|---|---|---|
| committer | Kent Overstreet <kent.overstreet@linux.dev> | 2024-10-20 16:50:14 -0400 |
| commit | f0d3302073e60b55318c941cd10b225a3cde9d32 (patch) | |
| tree | 506b94002e8908240c909c9b2e4a1a0c1ba1557f /drivers/gpu/drm/amd/amdgpu/amdgpu_sched.c | |
| parent | 3956ff8bc2f39a7e77d7a6da8d95c7ffc4928d64 (diff) | |
bcachefs: Workaround for kvmalloc() not supporting > INT_MAX allocations
kvmalloc() doesn't support allocations > INT_MAX, but vmalloc() does -
the limit should be lifted, but we can work around this for now.
A user with a 75 TB filesystem reported the following journal replay
error:
https://github.com/koverstreet/bcachefs/issues/769
In journal replay we have to sort and dedup all the keys from the
journal, which means we need a large contiguous allocation. Given that
the user has 128GB of ram, the 2GB limit on allocation size has become
far too small.
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_sched.c')
0 files changed, 0 insertions, 0 deletions