From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Sampath Peechu (speechu)" <speechu@cisco.com>,
"chenbo.xia@intel.com" <chenbo.xia@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Roger Melton (rmelton)" <rmelton@cisco.com>
Subject: Re: Commit broke 32-bit testpmd app
Date: Tue, 22 Nov 2022 10:23:51 +0100 [thread overview]
Message-ID: <827f912f-fc2d-6d41-ba8c-e7f3f9f2e24b@redhat.com> (raw)
In-Reply-To: <MN2PR11MB4581331F5C263CE604B44508BD049@MN2PR11MB4581.namprd11.prod.outlook.com>
Hi,
In my initial reply (see below), I also asked if you had logs to share.
And wondered whether it happens with Virtio PCI or Virtio-user?
Regards,
Maxime
On 11/16/22 00:30, Sampath Peechu (speechu) wrote:
> ++ dev@dpdk.org <mailto:dev@dpdk.org>
>
> *From: *Maxime Coquelin <maxime.coquelin@redhat.com>
> *Date: *Tuesday, November 15, 2022 at 3:19 AM
> *To: *Sampath Peechu (speechu) <speechu@cisco.com>, chenbo.xia@intel.com
> <chenbo.xia@intel.com>
> *Cc: *Roger Melton (rmelton) <rmelton@cisco.com>
> *Subject: *Re: Commit broke 32-bit testpmd app
>
> Hi Sampath,
>
>
> Please add dev@dpdk.org, the upstream mailing list, if this is related
> to the upstream DPDK project.If it is using RHEL DPDK package, please
> use the appropriate support channels.
>
> On 11/14/22 23:55, Sampath Peechu (speechu) wrote:
> > Hi Virtio Maintainers team,
> >
> > This email is regarding the following commit.
> >
> >
> https://github.com/DPDK/dpdk/commit/ba55c94a7ebc386d2288d6578ed57aad6cb92657 <https://github.com/DPDK/dpdk/commit/ba55c94a7ebc386d2288d6578ed57aad6cb92657> <https://github.com/DPDK/dpdk/commit/ba55c94a7ebc386d2288d6578ed57aad6cb92657 <https://github.com/DPDK/dpdk/commit/ba55c94a7ebc386d2288d6578ed57aad6cb92657>>
> >
> > The above commit appears to have broken the 32-bit testpmd app (and
> > consequently impacted one of our products that runs as a 32-bit DPDK
> > app). The 64-bit testpmd app does not appear to be impacted though.
>
> We'll need some logs to understand what is going on.
> Does it happen with virtio-pci or virtio-user?
>
> Regards,
> Maxime
>
> > With the commit in place, we didn’t see any packets going through at
> > all. After backing out the commit and rebuilding the 32-bit testpmd app
> > in our test setup, we were able to pass traffic as expected.
> >
> > Could you please let us know if this is a known issue? And if there is a
> > fix available for it?
> >
> > Thank you,
> >
> > Sampath Peechu
> >
> > Cisco Systems
> >
>
next prev parent reply other threads:[~2022-11-22 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MN2PR11MB45814151ACC8381ABFB1DCB9BD059@MN2PR11MB4581.namprd11.prod.outlook.com>
[not found] ` <63486764-3b44-3299-6830-05435dfd78f3@redhat.com>
2022-11-15 23:30 ` Sampath Peechu (speechu)
2022-11-22 9:23 ` Maxime Coquelin [this message]
2022-11-23 22:15 ` Sampath Peechu (speechu)
2022-12-06 18:08 ` Sampath Peechu (speechu)
2023-01-30 20:29 ` Sampath Peechu (speechu)
2023-03-24 0:49 ` Roger Melton (rmelton)
[not found] ` <MN2PR11MB458198A11C9CDA27C69FBA37BD1FA@MN2PR11MB4581.namprd11.prod.outlook.com>
2023-09-06 18:57 ` Dave Johnson (davejo)
2023-09-13 13:24 ` Roger Melton (rmelton)
2023-09-20 7:35 ` Maxime Coquelin
2023-09-20 13:05 ` Maxime Coquelin
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=827f912f-fc2d-6d41-ba8c-e7f3f9f2e24b@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=rmelton@cisco.com \
--cc=speechu@cisco.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).