From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org, "John Daley \(johndale\)" <johndale@cisco.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] enic: fix hash creation when not using first numa node
Date: Tue, 20 Oct 2015 21:34:02 +0200 [thread overview]
Message-ID: <2454209.3fpPk1zZ7K@xps13> (raw)
In-Reply-To: <D2188EC7.445DD%ssujith@cisco.com>
> >If dpdk is run with memory only available on socket != 0, then hash
> >creation will fail and flow director feature won't be available.
> >Fix this by asking for allocation on caller socket.
> >
> >Signed-off-by: David Marchand <david.marchand@6wind.com>
>
> Acked by: Sujith Sankar <ssujith@cisco.com>
Series applied, thanks.
next prev parent reply other threads:[~2015-10-20 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 8:02 [dpdk-dev] [PATCH 1/2] enic: fix allocation " David Marchand
2015-09-11 8:02 ` [dpdk-dev] [PATCH 2/2] enic: fix hash creation " David Marchand
2015-09-11 8:29 ` Sujith Sankar (ssujith)
2015-10-20 19:34 ` Thomas Monjalon [this message]
2015-09-11 8:28 ` [dpdk-dev] [PATCH 1/2] enic: fix allocation " Sujith Sankar (ssujith)
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=2454209.3fpPk1zZ7K@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=johndale@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).