diff options
author | Alexandru Moise <[email protected]> | 2015-08-27 23:53:45 +0000 |
---|---|---|
committer | David Sterba <[email protected]> | 2015-10-21 18:28:48 +0200 |
commit | f2f767e7345dfe56102d6809f647ba38a238f718 (patch) | |
tree | fc4496756c4c99ca7b08dbfa47c3d0f70b2aed62 /tools/perf/util/trace-event-scripting.c | |
parent | 0412e58c6d62168643a285f99b2354fa97df6cf3 (diff) |
btrfs: trimming some start_transaction() code away
Just call kmem_cache_zalloc() instead of calling kmem_cache_alloc().
We're just initializing most fields to 0, false and NULL later on
_anyway_, so to make the code mode readable and potentially gain
a bit of performance (completely untested claim), we should fill our
btrfs_trans_handle with zeros on allocation then just initialize
those five remaining fields (not counting the list_heads) as normal.
Reviewed-by: David Sterba <[email protected]>
Signed-off-by: Alexandru Moise <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions