From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v2 3/3] memif: : remove fallbacks for old Linux versions
Date: Tue, 19 Aug 2025 10:16:34 +0200 [thread overview]
Message-ID: <CAJFAV8x6BR=C82u=3UO+z4K1y4Roki_PL6uLkk=S9DCB0YrE0w@mail.gmail.com> (raw)
In-Reply-To: <20250728151908.338534-4-bruce.richardson@intel.com>
On Mon, Jul 28, 2025 at 5:19 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> All supported linux versions support F_ADD_SEALS (Linux 3.17+) and
> MFD_HUGETLB (Linux 4.14+), so no need to have #ifdefs and fallbacks to
> support systems which do not support those features.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> drivers/net/memif/rte_eth_memif.h | 41 -------------------------------
> 1 file changed, 41 deletions(-)
>
> diff --git a/drivers/net/memif/rte_eth_memif.h b/drivers/net/memif/rte_eth_memif.h
> index 8e45a3ab78..d4e625ab51 100644
> --- a/drivers/net/memif/rte_eth_memif.h
> +++ b/drivers/net/memif/rte_eth_memif.h
> @@ -169,37 +169,6 @@ int memif_init_regions_and_queues(struct rte_eth_dev *dev);
> */
> const char *memif_version(void);
>
> -#ifndef MFD_HUGETLB
> -#ifndef __NR_memfd_create
> -
> -#if defined __x86_64__
> -#define __NR_memfd_create 319
> -#elif defined __x86_32__
> -#define __NR_memfd_create 1073742143
> -#elif defined __arm__
> -#define __NR_memfd_create 385
> -#elif defined __aarch64__
> -#define __NR_memfd_create 279
> -#elif defined __powerpc__
> -#define __NR_memfd_create 360
> -#elif defined __i386__
> -#define __NR_memfd_create 356
> -#elif defined __riscv
> -#define __NR_memfd_create 279
> -#elif defined __loongarch__
> -#define __NR_memfd_create 279
> -#else
> -#error "__NR_memfd_create unknown for this architecture"
> -#endif
> -
> -#endif /* __NR_memfd_create */
> -
> -static inline int memfd_create(const char *name, unsigned int flags)
> -{
> - return syscall(__NR_memfd_create, name, flags);
> -}
> -#endif /* MFD_HUGETLB */
> -
> #ifndef F_LINUX_SPECIFIC_BASE
> #define F_LINUX_SPECIFIC_BASE 1024
> #endif
> @@ -208,14 +177,4 @@ static inline int memfd_create(const char *name, unsigned int flags)
> #define MFD_ALLOW_SEALING 0x0002U
> #endif
I suspect more stuff could be removed in this header.. but this is a
different topic than what the series deals with.
Thanks for the cleanup.
--
David Marchand
next prev parent reply other threads:[~2025-08-19 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 13:29 [PATCH 25.11 0/3] " Bruce Richardson
2025-06-30 13:29 ` [PATCH 25.11 1/3] eal/linux: " Bruce Richardson
2025-06-30 13:29 ` [PATCH 25.11 2/3] vhost: : " Bruce Richardson
2025-06-30 13:29 ` [PATCH 25.11 3/3] memif: " Bruce Richardson
2025-06-30 15:02 ` [PATCH 25.11 0/3] " Stephen Hemminger
2025-07-28 15:19 ` [PATCH v2 " Bruce Richardson
2025-07-28 15:19 ` [PATCH v2 1/3] eal/linux: " Bruce Richardson
2025-07-28 15:19 ` [PATCH v2 2/3] vhost: : " Bruce Richardson
2025-07-28 15:19 ` [PATCH v2 3/3] memif: " Bruce Richardson
2025-08-19 8:16 ` David Marchand [this message]
2025-07-30 9:21 ` [PATCH v2 0/3] " Morten Brørup
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='CAJFAV8x6BR=C82u=3UO+z4K1y4Roki_PL6uLkk=S9DCB0YrE0w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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).