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: dev <dev@dpdk.org>, Aaron Conole <aconole@redhat.com>,
	ci@dpdk.org,  Lincoln Lavoie <lylavoie@iol.unh.edu>
Subject: Re: [dpdk-dev] [PATCH v1 0/1] distributor test fix
Date: Tue, 19 Jan 2021 09:44:06 +0100
Message-ID: <CAJFAV8xyj7JyoyjMtfD1LA06hWYSg1iezS5BFqHyxiy=JgXXHg@mail.gmail.com> (raw)
In-Reply-To: <20210119035910.8324-1-l.wojciechow@partner.samsung.com>

On Tue, Jan 19, 2021 at 4:59 AM Lukasz Wojciechowski
<l.wojciechow@partner.samsung.com> wrote:
> According to the discussion in this thread:
> https://protect2.fireeye.com/v1/url?k=24ecce33-7b77f77c-24ed457c-0cc47a30
> d446-e317a6beb8cfa273&q=1&e=f8bb12df-3698-4bce-a7b7-d72e22b91431&u=https%
> 3A%2F%2Finbox.dpdk.org%2Fdev%2FCAOE1vsOehF4ZMOWffpEv%3DQF6YOc5wXtg23PV83B
> 9CLiTMn8wQA%40mail.gmail.com%2F%23r
> I was able to reproduce the distributor test failure in the exactly same
> way as described, but on x86_64 machine with 32 cores.
> So it does not seem to be the problem related to the ARM architecture.
> IMO issue occurs when there are many worker threads returning at the same
> time packets.
> I was not able to observe the issue on ARM devices, but I used only
> machines with 4 cores. So that is max 3 worker cores,
> so maximum of 32*3 = 96 packets processed at the same time
> which is less than 127 , so the issue cannot occur.
> Can anyone verify this patch on a machine similar to one used in CI lab,
> on which the issue occurred?

Thanks for looking at it, Lukasz.
Unfortunately, I can't reproduce it on my x86 system (26 workers in
the test) and I don't have a ARM machine.

David Marchand

  parent reply	other threads:[~2021-01-19  8:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210119035920eucas1p15da5a04b73d19e63287dc14905d765f2@eucas1p1.samsung.com>
2021-01-19  3:59 ` Lukasz Wojciechowski
     [not found]   ` <CGME20210119035921eucas1p1aaea0d68975ba9481f200912eb10a40e@eucas1p1.samsung.com>
2021-01-19  3:59     ` [dpdk-dev] [PATCH v1 1/1] test/distributor: prevent return buffer overload Lukasz Wojciechowski
2021-01-28 14:10       ` [dpdk-dev] [dpdk-stable] " David Marchand
2021-01-29  8:03         ` David Marchand
2021-01-29 12:36           ` Lukasz Wojciechowski
2021-01-28 16:46       ` [dpdk-dev] " David Hunt
2021-01-19  8:44   ` David Marchand [this message]
2021-01-19 13:06     ` [dpdk-dev] [PATCH v1 0/1] distributor test fix Lukasz Wojciechowski
2021-01-28 13:34       ` 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:

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

  git send-email \
    --in-reply-to='CAJFAV8xyj7JyoyjMtfD1LA06hWYSg1iezS5BFqHyxiy=JgXXHg@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=l.wojciechow@partner.samsung.com \
    --cc=lylavoie@iol.unh.edu \


* 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