From: "Zhoujian (jay)" <jianjay.zhou@huawei.com>
To: Xiao Wang <xiao.w.wang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Akhil Goyal <akhil.goyal@nxp.com>,
"Huangweidong (C)" <weidong.huang@huawei.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/virtio: alloc private data by NUMA affinity
Date: Tue, 8 Oct 2019 02:03:24 +0000 [thread overview]
Message-ID: <B2D15215269B544CADD246097EACE7473F1CAA6C@DGGEMM528-MBX.china.huawei.com> (raw)
In-Reply-To: <20190904132151.58885-1-xiao.w.wang@intel.com>
> -----Original Message-----
> From: Xiao Wang [mailto:xiao.w.wang@intel.com]
> Sent: Wednesday, September 4, 2019 9:22 PM
> To: Zhoujian (jay) <jianjay.zhou@huawei.com>
> Cc: dev@dpdk.org; Xiao Wang <xiao.w.wang@intel.com>
> Subject: [PATCH] crypto/virtio: alloc private data by NUMA affinity
>
> It's better to allocate device private data on the same NUMA node with device,
> rather than with the main thread. This helps avoid cross-NUMA access for
> worker thread.
>
> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
Reviewed-by: Jay Zhou <jianjay.zhou@huawei.com>
> ---
> drivers/crypto/virtio/virtio_cryptodev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/virtio/virtio_cryptodev.c
> b/drivers/crypto/virtio/virtio_cryptodev.c
> index f16bdfe57..4af479f54 100644
> --- a/drivers/crypto/virtio/virtio_cryptodev.c
> +++ b/drivers/crypto/virtio/virtio_cryptodev.c
> @@ -1441,7 +1441,7 @@ crypto_virtio_pci_probe( {
> struct rte_cryptodev_pmd_init_params init_params = {
> .name = "",
> - .socket_id = rte_socket_id(),
> + .socket_id = pci_dev->device.numa_node,
> .private_data_size = sizeof(struct virtio_crypto_hw)
> };
> char name[RTE_CRYPTODEV_NAME_MAX_LEN];
> --
> 2.15.1
next prev parent reply other threads:[~2019-10-08 2:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 13:21 Xiao Wang
2019-10-04 12:00 ` Akhil Goyal
2019-10-08 2:06 ` [dpdk-dev] 答复: " Zhoujian (jay)
2019-10-08 2:03 ` Zhoujian (jay) [this message]
2019-10-09 9:40 ` [dpdk-dev] " Akhil Goyal
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=B2D15215269B544CADD246097EACE7473F1CAA6C@DGGEMM528-MBX.china.huawei.com \
--to=jianjay.zhou@huawei.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=weidong.huang@huawei.com \
--cc=xiao.w.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).