From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: John Griffin <john.griffin@intel.com>
Cc: dev@dpdk.org, eoin.breen@intel.com, pablo.de.lara.guarch@intel.com
Subject: Re: [PATCH] crypto/qat: fix memzone creation to use a fixed size string
Date: Mon, 5 Sep 2016 11:23:56 +0800 [thread overview]
Message-ID: <20160905032356.GH30752@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1472725298-8455-1-git-send-email-john.griffin@intel.com>
On Thu, Sep 01, 2016 at 11:21:38AM +0100, John Griffin wrote:
> Remove the dependency on dev->driver->pci_drv.name when
> creating the memzone for the qat hardware queues.
> The pci_drv.name may grow too large for RTE_MEMZONE_NAMESIZE.
Will the "may grow too large" cause any issues? If so, state it here. If
not, marking this patch as a "fix" patch doesn't make sense to me then.
>
> Fixes: 1703e94ac5ce ("qat: add driver for QuickAssist devices")
>
> Signed-off-by: John Griffin <john.griffin@intel.com>
> ---
> drivers/crypto/qat/qat_qp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/qat/qat_qp.c b/drivers/crypto/qat/qat_qp.c
> index 5de47e3..a29ed66 100644
> --- a/drivers/crypto/qat/qat_qp.c
> +++ b/drivers/crypto/qat/qat_qp.c
> @@ -300,7 +300,7 @@ qat_queue_create(struct rte_cryptodev *dev, struct qat_queue *queue,
> * Allocate a memzone for the queue - create a unique name.
> */
> snprintf(queue->memz_name, sizeof(queue->memz_name), "%s_%s_%d_%d_%d",
> - dev->driver->pci_drv.name, "qp_mem", dev->data->dev_id,
> + "qat_pmd", "qp_mem", dev->data->dev_id,
Besides that, why not putting "qat_pmd" and "qp_mem" inside the format
string?
--yliu
next prev parent reply other threads:[~2016-09-05 3:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 10:21 [PATCH] crypto/qat: fix memzone creation to use a fixed size string John Griffin
2016-09-05 3:23 ` Yuanhan Liu [this message]
2016-09-14 15:32 ` John Griffin
2016-09-18 8:16 ` Yuanhan Liu
2016-09-19 10:12 ` John Griffin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160905032356.GH30752@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=eoin.breen@intel.com \
--cc=john.griffin@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.