DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "David Marchand" <david.marchand@redhat.com>, dev <dev@dpdk.org>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"Tyler Retzlaff" <roretzla@linux.microsoft.com>
Subject: Re: [PATCH] eal/x86: fix build on systems with WAITPKG support
Date: Mon, 28 Aug 2023 12:03:40 +0100	[thread overview]
Message-ID: <ZOx/DMLEK6oQW59S@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAOaVG17VkYUSnBg=A318wFmsrP4htA9LEuz6W+oeuqwVH8ZBnQ@mail.gmail.com>

On Mon, Aug 28, 2023 at 12:42:38PM +0200, Stephen Hemminger wrote:
>    For humor
>    #define RTE_CASTAWAY(x) ((void *)(uinptr_t)(x))

Yes, actually thought about that. Was also wondering about making it an
inline function rather than macro, to ensure its only used on pointers, and
to make clear what is being cast away:

static inline void *
rte_cast_no_volatile(volatile void *x)
{
	return (void *)(uintptr_t)(x);
}

and similarly we could do a rte_cast_no_const(const void *x).

WDYT?

/Bruce

  reply	other threads:[~2023-08-28 11:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 15:28 Bruce Richardson
2023-08-25 16:07 ` Morten Brørup
2023-08-28  7:08 ` David Marchand
2023-08-28  8:05   ` David Marchand
2023-08-28  9:29 ` David Marchand
2023-08-28 10:29   ` Bruce Richardson
2023-08-28 10:42     ` Stephen Hemminger
2023-08-28 11:03       ` Bruce Richardson [this message]
2023-08-28 14:31         ` Ferruh Yigit
2023-08-28 15:56         ` Tyler Retzlaff
2023-08-28 10:39 ` [PATCH v2] " Bruce Richardson
2023-08-28 14:39   ` David Marchand

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=ZOx/DMLEK6oQW59S@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=stephen@networkplumber.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).