From: Jerin Jacob <jerinjacobk@gmail.com>
To: pbhagavatula@marvell.com
Cc: jerinj@marvell.com, dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] doc: fix test eventdev example commands
Date: Tue, 9 Jan 2024 13:55:26 +0530 [thread overview]
Message-ID: <CALBAE1OjF1R8M_H_Sf=+Tj00qrGe3SDTHH14Mne8fLO4+S5E0A@mail.gmail.com> (raw)
In-Reply-To: <20240105155431.5639-1-pbhagavatula@marvell.com>
On Fri, Jan 5, 2024 at 9:24 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Fix incorrect core masks in testeventdev example
> commands.
>
> Fixes: f6dda59153f1 ("doc: add order queue test in eventdev test guide")
> Fixes: dd37027f2ba6 ("doc: add order all types queue test in eventdev test guide")
> Fixes: 43bc2fef79cd ("doc: add perf queue test in eventdev test guide")
> Fixes: b3d4e665ed3d ("doc: add perf all types queue test in eventdev test guide")
> Fixes: b01974da9f25 ("app/eventdev: add ethernet device producer option")
> Fixes: ba9de463abeb ("doc: add pipeline queue test in testeventdev guide")
> Fixes: d1b46daf7484 ("doc: add pipeline atq test in testeventdev guide")
> Fixes: d008f20bce23 ("app/eventdev: add event timer adapter as a producer")
> Fixes: 2eaa37b86635 ("app/eventdev: add vector mode in pipeline test")
> Cc: stable@dpdk.org
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> - sudo <build_dir>/app/dpdk-test-eventdev --vdev=event_octeontx -- \
> + sudo <build_dir>/app/dpdk-test-eventdev -c 0x1f --vdev=event_octeontx -- \
> --test=order_atq --plcores 1 --wlcores 2,3
Since you are here, Could you remove "--vdev=event_octeontx" from the
documentation, as there are
HW PMDs without vdev now. This doc was created there was only
event_octeontx PMD.
next prev parent reply other threads:[~2024-01-09 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 15:54 pbhagavatula
2024-01-09 8:25 ` Jerin Jacob [this message]
2024-02-01 19:33 ` [PATCH v2] " pbhagavatula
2024-02-01 19:37 ` [PATCH v3] " pbhagavatula
2024-02-02 7:57 ` 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='CALBAE1OjF1R8M_H_Sf=+Tj00qrGe3SDTHH14Mne8fLO4+S5E0A@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=stable@dpdk.org \
/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).