diff options
| author | Tyrel Datwyler <[email protected]> | 2021-01-14 14:31:30 -0600 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2021-01-14 22:27:43 -0500 |
| commit | 003d91a1393d7dad8351fd36eed90d6cb77dd232 (patch) | |
| tree | ddc658d30a958e62b10d123c020e347cdfc2b737 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 225acf5f1aba3b469c1f762cbd14cdb4bd7aefc5 (diff) | |
scsi: ibmvfc: Init/free event pool during queue allocation/free
The event pool and CRQ used to be separate entities of the adapter host
structure and as such were allocated and freed independently of each
other. Recent work as defined a generic queue structure with an event pool
specific to each queue. As such the event pool for each queue shouldn't be
allocated/freed independently, but instead performed as part of the queue
allocation/free routines.
Move the calls to ibmvfc_event_pool_{init|free} into
ibmvfc_{alloc|free}_queue respectively. The only functional change here is
that the CRQ cannot be released in ibmvfc_remove until after the event pool
has been successfully purged since releasing the queue will also free the
event pool.
Link: https://lore.kernel.org/r/[email protected]
Reviewed-by: Brian King <[email protected]>
Signed-off-by: Tyrel Datwyler <[email protected]>
Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions