DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
Cc: David Hunt <david.hunt@intel.com>, dev <dev@dpdk.org>,
	ci@dpdk.org,  Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-dev] distributor test failure in UNH CI on ARM
Date: Mon, 11 Jan 2021 14:04:09 +0100
Message-ID: <CAJFAV8yyL7AXxAHYu3-DiQw=mrE1Ey5pp=G2L-TZqPP-GAsuAA@mail.gmail.com> (raw)
In-Reply-To: <263e6c13-b87c-2fe0-36ef-ac6aa600c18f@partner.samsung.com>

On Mon, Jan 11, 2021 at 11:37 AM Lukasz Wojciechowski
<l.wojciechow@partner.samsung.com> wrote:
> I took a look at the logs. The issue appeared in testing big burst in
> sanity_test() for burst implementation of distributor.
> My guess is that the cyclic buffer for holding packets returned from
> workers might be overflown and dropping some of the packets. It's
> designed this way, to hold only 127 latest packets. Older, not collected
> on time with rte_distributor_returned_pkts(), are lost.
> Although it's just a guess until I can confirm it with some tests on my
> machine.

Why would it happen only on ARM?
My guess would be an arch-specific synchronisation issue?

> However the guess is possible, so the question is about the
> functionality of collecting the returned packets.
> We can:
> 1) keep it as is and fix tests not to send new packets until old ones
> are returned and collected
> 2) make changes to the distributor library and change behavior of the
> returned packages queue - however this requires some discussion as any
> solution will have its drawbacks (e.g. blocking workers until there is a
> place to store packets or using more space for the queue)
> Write, what do you think about it.
> Meanwhile I'll try to reproduce the issue

The distributor API is flagged as stable, so we can't change its API.
Solution 1) seems the way to go, but I'll wait for a rca.

David Marchand

  reply	other threads:[~2021-01-11 13:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210111081428eucas1p1f5f234cef3e3582ab8ba2726d8d105ea@eucas1p1.samsung.com>
2021-01-11  8:14 ` David Marchand
2021-01-11 10:37   ` Lukasz Wojciechowski
2021-01-11 13:04     ` David Marchand [this message]
2021-01-11 13:08   ` David Marchand
2021-01-11 13:54     ` Jerin Jacob
2021-01-11 13:56       ` Lincoln Lavoie
2021-01-11 14:04         ` Jerin Jacob
2021-01-11 14:19           ` [dpdk-dev] [dpdklab] " Lincoln Lavoie
2021-01-19  4:02             ` Lukasz Wojciechowski

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJFAV8yyL7AXxAHYu3-DiQw=mrE1Ey5pp=G2L-TZqPP-GAsuAA@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=l.wojciechow@partner.samsung.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git