btrfs: use generic slab for for btrfs_transaction

Browse source

Observing the number of slab objects of btrfs_transaction, there's just
one active on an almost quiescent filesystem, and the number of objects
goes to about ten when sync is in progress. Then the nubmer goes down to
1.  This matches the expectations of the transaction lifetime.

For such use the separate slab cache is not justified, as we do not
reuse objects frequently. For the shortlived transaction, the generic
slab (size 512) should be ok. We can optimistically expect that the 512
slabs are not all used (fragmentation) and there are free slots to take
when we do the allocation, compared to potentially allocating a whole new
page for the separate slab.

We'll lose the stats about the object use, which could be added later if
we really need them.

Signed-off-by: David Sterba <dsterba@suse.com>

...

This commit is contained in:

David Sterba 2017-03-28 12:06:05 +02:00

parent 3fb99303c6

commit 4b5faeac46

4 changed files with 4 additions and 18 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

1

fs/btrfs/ctree.h

View file

5

fs/btrfs/disk-io.c

View file

8

fs/btrfs/inode.c

View file

8

fs/btrfs/transaction.c

View file