DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Junxiao Shi <git@mail1.yoursunny.com>,
	Jakub Grajciar <jgrajcia@cisco.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/memif: allocate socket hash on any NUMA socket
Date: Thu, 30 Sep 2021 14:31:37 +0100	[thread overview]
Message-ID: <d6728d6b-9501-c517-9380-4078f6641cd0@intel.com> (raw)
In-Reply-To: <973fc5b37c6164c1@cs.arizona.edu>

On 9/28/2021 2:51 PM, Junxiao Shi wrote:
> Previously, memif socket hash is always allocated on NUMA socket 0.
> If the application is entirely running on another NUMA socket and EAL
> --socket-limit prevents memory allocation on NUMA socket 0, memif
> creation fails with "HASH: memory allocation failed" error.
> 
> This patch allows allocating memif socket hash on any NUMA socket.
> 
> Signed-off-by: Junxiao Shi <git@mail1.yoursunny.com>
> ---
>  drivers/net/memif/memif_socket.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/net/memif/memif_socket.c b/drivers/net/memif/memif_socket.c
> index f58ff4c0cb..364e818d65 100644
> --- a/drivers/net/memif/memif_socket.c
> +++ b/drivers/net/memif/memif_socket.c
> @@ -946,6 +946,7 @@ memif_create_socket_hash(void)
>  	params.key_len = MEMIF_SOCKET_UN_SIZE;
>  	params.hash_func = rte_jhash;
>  	params.hash_func_init_val = 0;
> +	params.socket_id = SOCKET_ID_ANY;
>  	return rte_hash_create(&params);
>  }
>  
> 

looks good to me. cc'ed the memif maintainer.

  reply	other threads:[~2021-09-30 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 13:51 Junxiao Shi
2021-09-30 13:31 ` Ferruh Yigit [this message]
2021-10-04 12:02   ` Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco)
2021-10-04 17:29     ` Ferruh Yigit

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=d6728d6b-9501-c517-9380-4078f6641cd0@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=git@mail1.yoursunny.com \
    --cc=jgrajcia@cisco.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).