From: John Griffin <john.griffin@intel.com>
To: Yuanhan Liu <yuanhan.liu@linux.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, 19 Sep 2016 11:12:15 +0100 [thread overview]
Message-ID: <57DFB9FF.5090907@intel.com> (raw)
In-Reply-To: <20160918081643.GE23158@yliu-dev.sh.intel.com>
On 18/09/16 09:16, Yuanhan Liu wrote:
> On Wed, Sep 14, 2016 at 04:32:46PM +0100, John Griffin wrote:
>> Hi Liu,
>> Comments embedded.
>>
>> Rgds,
>> John.
>>
>> On 05/09/16 04:23, Yuanhan Liu wrote:
>>> 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.
>> We discovered this when applying a future patch (2141c21966) and it exposed
>> this issue.
>> Problem is we create a memzone per hardware queue pair and if the memzone
>> name is too large, then this code will not produce a unique
>> name and two qps will end using the same memzone.
>
> Thanks for the info, and I think you should put it in the commit log: it
> helps people to really know what might go wrong without this fix.
>
> --yliu
>
No problem. Yes will add to the v2.
Rgds,
John.
prev parent reply other threads:[~2016-09-19 10: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
2016-09-14 15:32 ` John Griffin
2016-09-18 8:16 ` Yuanhan Liu
2016-09-19 10:12 ` John Griffin [this message]
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=57DFB9FF.5090907@intel.com \
--to=john.griffin@intel.com \
--cc=dev@dpdk.org \
--cc=eoin.breen@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=yuanhan.liu@linux.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.