DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
To: David Marchand <david.marchand@redhat.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 14:06:57 +0100	[thread overview]
Message-ID: <0a27bf29-8baa-1fcd-837c-acebb155cdf0@partner.samsung.com> (raw)
In-Reply-To: <CAJFAV8xyj7JyoyjMtfD1LA06hWYSg1iezS5BFqHyxiy=JgXXHg@mail.gmail.com>

Thank you David,
If you have the possibility you can try on some emulated virtual 
machine, where cores are much slower, so the workers don't return 
packages immediately.
It reproduces in 100% cases in such environment.

Best regards

Lukasz

W dniu 19.01.2021 o 09:44, David Marchand pisze:
> 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.
>
-- 
Lukasz Wojciechowski
Principal Software Engineer

Samsung R&D Institute Poland
Samsung Electronics
Office +48 22 377 88 25
l.wojciechow@partner.samsung.com


  reply	other threads:[~2021-01-19 13:07 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   ` [dpdk-dev] [PATCH v1 0/1] distributor test fix David Marchand
2021-01-19 13:06     ` Lukasz Wojciechowski [this message]
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:
  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=0a27bf29-8baa-1fcd-837c-acebb155cdf0@partner.samsung.com \
    --to=l.wojciechow@partner.samsung.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    /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).