diff options
| author | Brian Behlendorf <[email protected]> | 2014-12-03 14:56:32 -0500 |
|---|---|---|
| committer | Brian Behlendorf <[email protected]> | 2015-01-16 14:40:32 -0800 |
| commit | efcd79a883caddea4a20bfc771da31ecc6ce4ca2 (patch) | |
| tree | 3eb615043ffa64d2a7729aa6450c1326cb62f40e /module/zfs/zio.c | |
| parent | 71f8548ea443718a5afb1598f1f3a27a369ccd8b (diff) | |
Retire KM_NODEBUG
Callers of kmem_alloc() which passed the KM_NODEBUG flag to suppress
the large allocation warning have been replaced by vmem_alloc() as
appropriate. The updated vmem_alloc() call will not print a warning
regardless of the size of the allocation.
A careful reader will notice that not all callers have been changed
to vmem_alloc(). Some have only had the KM_NODEBUG flag removed.
This was possible because the default warning threshold has been
increased to 32k. This is desirable because it minimizes the need
for Linux specific code changes.
Signed-off-by: Brian Behlendorf <[email protected]>
Diffstat (limited to 'module/zfs/zio.c')
| -rw-r--r-- | module/zfs/zio.c | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/module/zfs/zio.c b/module/zfs/zio.c index 7c0e6bf7e..d7c8458f4 100644 --- a/module/zfs/zio.c +++ b/module/zfs/zio.c @@ -246,7 +246,7 @@ zio_buf_alloc(size_t size) ASSERT3U(c, <, SPA_MAXBLOCKSIZE >> SPA_MINBLOCKSHIFT); - return (kmem_cache_alloc(zio_buf_cache[c], KM_PUSHPAGE | KM_NODEBUG)); + return (kmem_cache_alloc(zio_buf_cache[c], KM_PUSHPAGE)); } /* @@ -262,8 +262,7 @@ zio_data_buf_alloc(size_t size) ASSERT(c < SPA_MAXBLOCKSIZE >> SPA_MINBLOCKSHIFT); - return (kmem_cache_alloc(zio_data_buf_cache[c], - KM_PUSHPAGE | KM_NODEBUG)); + return (kmem_cache_alloc(zio_data_buf_cache[c], KM_PUSHPAGE)); } void |