On Thu, 2019-06-20 at 07:03 +0000, Saeed Mahameed wrote: > From: Matthew Wilcox <willy@xxxxxxxxxxxxx> > > The lock protecting the data structure does not need to be an > rwlock. The > only read access to the lock is in an error path, and if that's > limiting > your scalability, you have bigger performance problems. > > Eliminate mlx5_mkey_table in favour of using the xarray directly. > reg_mr_callback must use GFP_ATOMIC for allocating XArray nodes as it > may > be called in interrupt context. > > This also fixes a minor bug where SRCU locking was being used on the > radix > tree read side, when RCU was needed too. > > Change-Id: Ifeedbbc8f2c856cc044094d03167aae9f9162400 > Signed-off-by: Matthew Wilcox <willy@xxxxxxxxxxxxx> > Signed-off-by: Jason Gunthorpe <jgg@xxxxxxxxxxxx> > Signed-off-by: Saeed Mahameed <saeedm@xxxxxxxxxxxx> > Applied to mlx5-next. Thanks, Saeed.
