From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH 1/2] event/octeontx2: remove selftest from dev args
Date: Thu, 19 Nov 2020 13:30:59 +0000 [thread overview]
Message-ID: <BN6PR18MB114082D96F04D5E6B35E621FDEE00@BN6PR18MB1140.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8xErYjNiPgCH02JmeEu7sC-1SabkZqAZUYsg7PWBFhBuA@mail.gmail.com>
>On Thu, Nov 19, 2020 at 1:24 PM <pbhagavatula@marvell.com> wrote:
>>
>> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>>
>> Since selftest now depends on dynamic mbuf fields it is not
>> feasible to run selftest on device probe.
>
>Indeed, this is something that I missed with the seqn rework.
>Can't you call rte_event_dev_selftest() from within the pmd?
>
We can but generally selftest is run as a safety net before an
custom application runs but now since selftest uses dynamic
mbuf fields the custom application would be starved of that
field since there is no way to unregister it.
Regards,
Pavan.
>
>--
>David Marchand
next prev parent reply other threads:[~2020-11-19 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 12:23 [dpdk-dev] " pbhagavatula
2020-11-19 12:23 ` [dpdk-dev] [PATCH 2/2] event/octeontx: " pbhagavatula
2020-11-19 13:15 ` [dpdk-dev] [PATCH 1/2] event/octeontx2: " David Marchand
2020-11-19 13:30 ` Pavan Nikhilesh Bhagavatula [this message]
2020-11-19 13:36 ` [dpdk-dev] [EXT] " David Marchand
2020-11-19 13:45 ` Pavan Nikhilesh Bhagavatula
2020-11-19 13:57 ` [dpdk-dev] [PATCH v2 " pbhagavatula
2020-11-19 13:57 ` [dpdk-dev] [PATCH v2 2/2] event/octeontx: " pbhagavatula
2020-11-20 12:26 ` Jerin Jacob
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=BN6PR18MB114082D96F04D5E6B35E621FDEE00@BN6PR18MB1140.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
/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).