DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev <dev@dpdk.org>, "Pattan, Reshma" <reshma.pattan@intel.com>,
	dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] test: fix forwarding packets through not-ready port
Date: Tue, 26 Oct 2021 17:39:39 +0200	[thread overview]
Message-ID: <CAJFAV8xKSKp0R0wXhspTXcy66i_M6RfVNCkoNy_0yZcEsoWL_Q@mail.gmail.com> (raw)
In-Reply-To: <20211026111943.19957-1-konstantin.ananyev@intel.com>

On Tue, Oct 26, 2021 at 1:20 PM Konstantin Ananyev
<konstantin.ananyev@intel.com> wrote:
>
> (bitratestats_autotest|latencystats_autotest|pdump_autotest) tests
> generate a log of error messages like that:
>
> test_packet_forward() line 104: Error sending packet to port 0
> Send pkts Failed
>
> These tests use of app/test/sample_packet_forward.* code.
> This code creates a portid from a ring, but doesn't properly
> configure/start it.
> The fix adds code to configure/start given port before usage.
>
> Fixes: 7a0935239b9e ("ethdev: make fast-path functions to use new flat array")
> Fixes: a52966cd48fd ("test: add helpers using ring PMD Rx/Tx")
> Cc: stable@dpdk.org
>
> Reported-by: David Marchand <david.marchand@redhat.com>
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Tested-by: David Marchand <david.marchand@redhat.com>

Thanks for the fix.


-- 
David Marchand


  reply	other threads:[~2021-10-26 15:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 11:19 Konstantin Ananyev
2021-10-26 15:39 ` David Marchand [this message]
2021-10-26 17:57   ` David Marchand

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=CAJFAV8xKSKp0R0wXhspTXcy66i_M6RfVNCkoNy_0yZcEsoWL_Q@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=reshma.pattan@intel.com \
    --cc=stable@dpdk.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).