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-ci] [dpdk-dev] [PATCH v1 0/1] distributor test fix
Date: Thu, 28 Jan 2021 14:34:20 +0100 [thread overview]
Message-ID: <CAJFAV8xUz1cybWHmX_dr1Mk-8gdeL=vHXrtit4Uahu84rtK7Zg@mail.gmail.com> (raw)
In-Reply-To: <0a27bf29-8baa-1fcd-837c-acebb155cdf0@partner.samsung.com>
On Tue, Jan 19, 2021 at 2:07 PM Lukasz Wojciechowski
<l.wojciechow@partner.samsung.com> wrote:
>
> 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.
I reproduced the issue with starting a testpmd on the same cores in this system.
I usually reproduce it after 1-2 minutes of continuously running the
distributor_autotest unit test.
I've applied your fix in my tree and I will let this loop run for a while.
--
David Marchand
next prev parent reply other threads:[~2021-01-28 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210119035920eucas1p15da5a04b73d19e63287dc14905d765f2@eucas1p1.samsung.com>
[not found] ` <20210119035910.8324-1-l.wojciechow@partner.samsung.com>
2021-01-19 8:44 ` David Marchand
2021-01-19 13:06 ` Lukasz Wojciechowski
2021-01-28 13:34 ` David Marchand [this message]
[not found] ` <20210119035910.8324-2-l.wojciechow@partner.samsung.com>
[not found] ` <CAJFAV8ws=mCTFF6hQQ8kUFRxuR8QYGzB7ubMFRBDCiU=JmEnZQ@mail.gmail.com>
2021-01-29 8:03 ` [dpdk-ci] [dpdk-stable] [PATCH v1 1/1] test/distributor: prevent return buffer overload David Marchand
2021-01-29 12:36 ` 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:
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='CAJFAV8xUz1cybWHmX_dr1Mk-8gdeL=vHXrtit4Uahu84rtK7Zg@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 \
/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).