DPDK patches and discussions
 help / color / mirror / Atom feed
From: Wei Hu <weh@microsoft.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
	"dev@dpdk.org" <dev@dpdk.org>, Long Li <longli@microsoft.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	Kevin Traynor <ktraynor@redhat.com>,
	 Luca Boccassi <bluca@debian.org>
Subject: RE: [PATCH v2 1/1] net/mana: enable 32 bit build for mana driver
Date: Tue, 19 Sep 2023 02:44:43 +0000	[thread overview]
Message-ID: <SI2P153MB0441C45FC7C15601E4FB2278BBFAA@SI2P153MB0441.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <0505477b-36ed-4b6a-9970-d94858bdf59d@amd.com>

> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@amd.com>
> Sent: Tuesday, September 19, 2023 1:41 AM
> To: Wei Hu <weh@microsoft.com>; dev@dpdk.org; Long Li
> <longli@microsoft.com>
> Cc: stable@dpdk.org; Kevin Traynor <ktraynor@redhat.com>; Luca Boccassi
> <bluca@debian.org>
> Subject: Re: [PATCH v2 1/1] net/mana: enable 32 bit build for mana driver
> 
> On 9/13/2023 1:23 PM, Wei Hu wrote:
> > Enable 32 bit build on x86 Linux. Fixed build warnings and errors when
> > building in 32 bit.
> >
> > Cc: stable@dpdk.org
> >
> 
> This is not a fix, but adding 32bit support to the driver, so not sure about
> backporting. cc'ed Kevin & Luca for guidance.
> 
> I will drop the tag while merging unles otherwise suggested by LTS
> maintainers.

Hi Ferruh,

We have a customer who needs it to be on 22.11.x. That is why I put "Cc: stable@dpdk.org" in it.

> 
> > Signed-off-by: Wei Hu <weh@microsoft.com>
> >
> 
> Hi Wei,
> 
> Patch looks good, but it basically fixes the format specifiers that will cause
> build error for 32 bit.
> 
> Is there any other change required to make driver functional for 32 bit, or does
> it become functional with this change?
> And if it does can you please confirm explicityly that driver tested on
> 32 bit with this patch?

Another patch, " net/mana: add 32 bit short doorbell", is required to make mana fully
functional  with 32 bit applications. This patch is to fix some build time errors and warnings
when build in 32 bit.  These patches can be independently built and they are addressing
two different issues. So, I put them into two independent patches. 

I have tested it on 32 bit applications. They can run with this patch. Just mana would not
work as the applications still use 64 bit long door bells, which do not work for 32 bit apps.

Thanks,
Wei

  reply	other threads:[~2023-09-19  2:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 12:23 Wei Hu
2023-09-18 17:40 ` Ferruh Yigit
2023-09-19  2:44   ` Wei Hu [this message]
2023-09-19 11:05     ` Ferruh Yigit
2023-09-20  3:06       ` Wei Hu
2023-09-20 10:03         ` Ferruh Yigit
2023-09-20 11:22           ` Kevin Traynor

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=SI2P153MB0441C45FC7C15601E4FB2278BBFAA@SI2P153MB0441.APCP153.PROD.OUTLOOK.COM \
    --to=weh@microsoft.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=ktraynor@redhat.com \
    --cc=longli@microsoft.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).