Re: [PATCH] Btrfs: don't kzalloc the ordered extents

On 06.04.2011 01:20, Josef Bacik wrote: We initialize almost all of the fields when we allocate an ordered extent, so use kmalloc instead of kzalloc and just initialize the other fields that we don't already initialize yet. Thanks, Is it really worth it? we have seen a few bugs in the past

Re: [PATCH] Btrfs: don't kzalloc the ordered extents

Excerpts from Arne Jansen's message of 2011-04-06 03:54:07 -0400: On 06.04.2011 01:20, Josef Bacik wrote: We initialize almost all of the fields when we allocate an ordered extent, so use kmalloc instead of kzalloc and just initialize the other fields that we don't already initialize

Re: [PATCH] Btrfs: don't kzalloc the ordered extents

On 04/06/2011 07:06 AM, Chris Mason wrote: Excerpts from Arne Jansen's message of 2011-04-06 03:54:07 -0400: On 06.04.2011 01:20, Josef Bacik wrote: We initialize almost all of the fields when we allocate an ordered extent, so use kmalloc instead of kzalloc and just initialize the other fields

[PATCH] Btrfs: don't kzalloc the ordered extents

We initialize almost all of the fields when we allocate an ordered extent, so use kmalloc instead of kzalloc and just initialize the other fields that we don't already initialize yet. Thanks, Signed-off-by: Josef Bacik jo...@redhat.com --- fs/btrfs/ordered-data.c |4 +++- 1 files changed, 3