DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>, <dev@dpdk.org>
Cc: <stable@dpdk.org>, <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/af_xdp: disable secondary process support
Date: Fri, 8 Oct 2021 12:06:44 +0100	[thread overview]
Message-ID: <745d97f5-5082-31e2-644c-2a38047b6b04@intel.com> (raw)
In-Reply-To: <20211008075020.22003-1-ciara.loftus@intel.com>

On 10/8/2021 8:50 AM, Ciara Loftus wrote:
> Since the AF_XDP PMD does not work for secondary processes as reported
> in Bugzilla 805, check for the process type at the beginning of probe
> and return ENOTSUP if the process type is secondary.
> 
> It is planned that secondary processes will be supported by the PMD in
> full in a future release by using rte_mp_msg to pass the state to the
> secondary process that it requires in order to work.
> 
> Bugzilla ID: 805
> Fixes: f1debd77efaf ("net/af_xdp: introduce AF_XDP PMD")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> Reported-by: Stephen Hemminger <stephen@networkplumber.org>

Acked-by: Stephen Hemminger <stephen@networkplumber.org>

Applied to dpdk-next-net/main, thanks.


      reply	other threads:[~2021-10-08 11:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 13:46 [dpdk-dev] [PATCH] net/af_xdp: do not attempt probe for secondary processes Ciara Loftus
2021-09-30 15:18 ` Stephen Hemminger
2021-10-05 15:06 ` Ferruh Yigit
2021-10-08  7:50 ` [dpdk-dev] [PATCH v2] net/af_xdp: disable secondary process support Ciara Loftus
2021-10-08 11:06   ` Ferruh Yigit [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=745d97f5-5082-31e2-644c-2a38047b6b04@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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).