From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: dev@dpdk.org, navasile@linux.microsoft.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] eal/headers: explicitly cast void * to type *
Date: Thu, 14 Jan 2021 19:49:38 +0100 [thread overview]
Message-ID: <178962143.vrpKgbl6Nm@thomas> (raw)
In-Reply-To: <20210114212740.3d69dbc2@sovereign>
14/01/2021 19:27, Dmitry Kozlyuk:
> > > If it's a public header then maybe it's missing a @file?
> > >
> > My 2c on this in general...
> >
> > The use of public vs private headers is not always clear, sadly, in DPDK,
> > for historical reasons. With the make builds, libraries picked up headers
> > from other libraries via the "include" folder for all of DPDK, meaning that
> > if a particular header was internal only but used by multiple other libs,
> > it was placed in "include" for simplicity, rather than having each library
> > using it having to have separate "-I/path/to/header" cflags specified.
> > With the switch to meson, this common folder use is no longer be the case,
> > but because of the old way of doing things it may be that in the transition
> > some private headers were inadvertently kept as public (and possibly vice
> > versa, though that is more likely to be spotted by now).
> >
> > /Bruce
>
> Here is why rte_ethdev_pci.h should be considered private to DPDK:
>
> * rte_eth_copy_pci_info - intended for device init, that is, driver job
> * eth_dev_pci_specific_init - wrapper for the above
> * rte_eth_dev_pci_allocate - @internal, deals with private data
> * rte_eth_dev_pci_generic_probe - @internal, deals with private data
> * rte_eth_dev_pci_generic_remove - @internal
Yes rte_ethdev_pci.h is a helper for ethdev drivers,
it is DPDK internal.
next prev parent reply other threads:[~2021-01-14 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1610414325-9104-1-git-send-email-roretzla@linux.microsoft.com>
2021-01-13 17:52 ` [dpdk-stable] " Dmitry Kozlyuk
2021-01-14 5:45 ` Tyler Retzlaff
2021-01-14 7:05 ` Dmitry Kozlyuk
2021-01-14 10:55 ` Bruce Richardson
2021-01-14 18:27 ` Dmitry Kozlyuk
2021-01-14 18:49 ` Thomas Monjalon [this message]
2021-01-15 19:21 ` Tyler Retzlaff
2021-01-17 17:13 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2021-01-15 19:38 ` [dpdk-stable] [PATCH v2] eal/windows: " Tyler Retzlaff
2021-01-17 17:19 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2021-01-17 18:10 ` Stephen Hemminger
2021-01-17 19:51 ` Dmitry Kozlyuk
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=178962143.vrpKgbl6Nm@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=navasile@linux.microsoft.com \
--cc=roretzla@linux.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).