[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1637789139.git.christophe.jaillet@wanadoo.fr>
Date: Wed, 24 Nov 2021 22:30:08 +0100
From: Christophe JAILLET <christophe.jaillet@...adoo.fr>
To: bharat@...lsio.com, dledford@...hat.com, jgg@...pe.ca
Cc: linux-rdma@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org,
Christophe JAILLET <christophe.jaillet@...adoo.fr>
Subject: [PATCH 0/3] Cleanup and optimize a few bitmap operations
Patch 1 and 2 are just cleanups that uses 'bitmap_zalloc()' and 'bitmap_set()'
instead of hand-writing these functions.
Patch 3 is more questionable. It replaces calls to '[set|clear]_bit()' by their
non-atomic '__[set|clear]_bit()' alternatives.
It looks safe to do so because accesses to the corresponding bitmaps are
protected by spinlocks.
However, this patch is compile-tested only. It is not sure that it worth
changing the code just for saving a few atomic operations.
So review, test and apply only if it make sense.
Christophe JAILLET (3):
RDMA/cxgb4: Use bitmap_zalloc() when applicable
RDMA/cxgb4: Use bitmap_set() when applicable
RDMA/cxgb4: Use non-atomic bitmap functions when possible
drivers/infiniband/hw/cxgb4/id_table.c | 17 ++++++-----------
1 file changed, 6 insertions(+), 11 deletions(-)
--
2.30.2
Powered by blists - more mailing lists