DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, ferruh.yigit@amd.com,
	Tyler Retzlaff <roretzla@linux.microsoft.com>,
	Pallavi Kadam <pallavi.kadam@intel.com>,
	Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Subject: Re: [PATCH] eal/windows: define standard file numbers
Date: Thu, 10 Oct 2024 23:41:03 +0200	[thread overview]
Message-ID: <2067452.jZfb76A358@thomas> (raw)
In-Reply-To: <20241010153303.7e4318bc@sovereign>

10/10/2024 14:33, Dmitry Kozlyuk:
> 2024-10-10 12:39 (UTC+0100), Bruce Richardson:
> > On Thu, Oct 10, 2024 at 01:43:41PM +0300, Dmitry Kozlyuk wrote:
> > > 2024-10-10 10:54 (UTC+0100), Bruce Richardson:  
> > > > The macros for STD*_FILENO are missing on windows. Add defines for them
> > > > to the DPDK-local unistd.h file.
> > > > 
> > > > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > > > ---
> > > >  lib/eal/windows/include/unistd.h | 11 +++++++++++
> > > >  1 file changed, 11 insertions(+)
> > > > 
> > > > diff --git a/lib/eal/windows/include/unistd.h b/lib/eal/windows/include/unistd.h
> > > > index 6b33005b24..78150c6480 100644
> > > > --- a/lib/eal/windows/include/unistd.h
> > > > +++ b/lib/eal/windows/include/unistd.h
> > > > @@ -12,4 +12,15 @@
> > > >  
> > > >  #include <io.h>
> > > >  
> > > > +/*
> > > > + * Windows appears to be missing STD*_FILENO macros, so define here.
> > > > + * For simplicity, assume that if STDIN_FILENO is missing, all are,
> > > > + * rather than checking each individually.
> > > > + */
> > > > +#ifndef STDIN_FILENO
> > > > +#define STDIN_FILENO _fileno(stdin)
> > > > +#define STDOUT_FILENO _fileno(stdout)
> > > > +#define STDERR_FILENO _fileno(stderr)
> > > > +#endif
> > > > +
> > > >  #endif /* _UNISTD_H_ */  
> > > 
> > > Why is this needed?
> > > There are 3 users of STD*_FILENO within DPDK:
> > > * lib/eal/unix/eal_debug.c - not for Windows, obviously
> > > * app/dumpcap - not for Windows, requires multi-process
> > > * app/proc-info - not for Windows, requires multi-process
> > > * examples/l2fwd-cat - not for Windows, requires <pqos.h>  
> > 
> > https://patches.dpdk.org/project/dpdk/patch/20240822104109.116208-2-bruce.richardson@intel.com/
> > 
> > This merged patch is now throwing errors about the missing defines on
> > Windows.
> 
> Thanks, I was searching some outdated source.
> 
> Currently, <rte_os_shim.h> contains at least `read()`, `write()`,
> and `unlink()` which POSIX places in <unistd.h>.
> I wonder whether all that stuff should be moved into EAL's <unistd.h>
> or, on the opposite, <rte_os_shim.h> should consume all other shims.
> But that would be a broader refactoring, so for the fix:
> 
> Acked-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>

Applied, thanks.




      reply	other threads:[~2024-10-10 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  9:54 Bruce Richardson
2024-10-10 10:43 ` Dmitry Kozlyuk
2024-10-10 11:39   ` Bruce Richardson
2024-10-10 12:33     ` Dmitry Kozlyuk
2024-10-10 21:41       ` Thomas Monjalon [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=2067452.jZfb76A358@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=ferruh.yigit@amd.com \
    --cc=pallavi.kadam@intel.com \
    --cc=roretzla@linux.microsoft.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).