DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: Wisam Jaddo <wisamm@nvidia.com>,
	dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] test-flow-perf: Enable to build on Windows
Date: Tue, 2 Sep 2025 10:11:05 +0200	[thread overview]
Message-ID: <CAJFAV8yhjevtCqORT=baHT+sSX1sPALhzYoEB9DVo67WnZjx7Q@mail.gmail.com> (raw)
In-Reply-To: <20250830002333.GA6088@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>

Hello,

On Sat, 30 Aug 2025 at 02:23, Andre Muezerie
<andremue@linux.microsoft.com> wrote:
>
> On Fri, Aug 29, 2025 at 03:04:10PM +0200, David Marchand wrote:
> > Hello,
> >
> > On Tue, 5 Aug 2025 at 22:00, Andre Muezerie
> > <andremue@linux.microsoft.com> wrote:
> > >
> > > This patch fixes some issues which were preventing this test to be
> > > built on Windows:
> > >
> > > - Remove VLAs (not supported by msvc).
> > > - Replace strsep() (which is not natively available on Windows)
> > >   with strtok_r().
> > > - Remove the "thousands" separator from printf() calls as it is
> > >   not available on Windows.
> >
> > Can we use rte_size_to_str() instead?
> >
>
> I considered doing that, but I thought that since the app is printing deltas it
> could be better to print the exact numbers instead of some approximation like
> "1.02 k" which could possibly make debugging harder.
>
> If you strongly believe that rte_size_to_str() should indeed be used here I can
> make the change.
>
> What are your thoughts about this?

No strong opinion: just that we introduced this rte_size_to_str() for
this "thousands" separator stuff.
I don't mind merging as is, and I did not hear from Wisam, so I guess
this is fine.


-- 
David Marchand


      reply	other threads:[~2025-09-02  8:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 19:59 Andre Muezerie
2025-08-29 13:04 ` David Marchand
2025-08-30  0:23   ` Andre Muezerie
2025-09-02  8:11     ` David Marchand [this message]

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='CAJFAV8yhjevtCqORT=baHT+sSX1sPALhzYoEB9DVo67WnZjx7Q@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=andremue@linux.microsoft.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=wisamm@nvidia.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).