diff options
| author | James Smart <jsmart2021@gmail.com> | 2017-05-16 01:20:45 +0300 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2017-05-17 04:21:47 +0300 |
| commit | 6c621a2229b084da0d926967f84b059a10c26ede (patch) | |
| tree | 80c0e96ed57c386177a371039d36d3312f9951c5 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 3c603be9798758dde794daa622e0f7017dbff3a7 (diff) | |
| download | linux-6c621a2229b084da0d926967f84b059a10c26ede.tar.xz | |
scsi: lpfc: Separate NVMET RQ buffer posting from IO resources SGL/iocbq/context
Currently IO resources are mapped 1 to 1 with RQ buffers posted
Added logic to separate RQE buffers from IO op resources
(sgl/iocbq/context). During initialization, the driver will determine
how many SGLs it will allocate for NVMET (based on what the firmware
reports) and associate a NVMET IOCBq and NVMET context structure with
each one.
Now that hdr/data buffers are immediately reposted back to the RQ, 512
RQEs for each MRQ is sufficient. Also, since NVMET data buffers are now
128 bytes, lpfc_nvmet_mrq_post is not necessary anymore as we will
always post the max (512) buffers per NVMET MRQ.
Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com>
Signed-off-by: James Smart <james.smart@broadcom.com>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions