DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Christensen <drc@linux.ibm.com>
To: David Christensen <drc@linux.vnet.ibm.com>,
	thomas@monjalon.net, Ruifeng Wang <ruifeng.wang@arm.com>,
	Tyler Retzlaff <roretzla@linux.microsoft.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Min Zhou <zhoumin@loongson.cn>,
	Stanislaw Kardach <stanislaw.kardach@gmail.com>,
	Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Cc: dev@dpdk.org
Subject: Re: [PATCH v5] eal: verify mmu type for DPDK support (ppc64le)
Date: Thu, 27 Jun 2024 14:11:57 -0700	[thread overview]
Message-ID: <81a9db62-18db-4bbc-a27b-a941d9c55016@linux.ibm.com> (raw)
In-Reply-To: <20240529183222.105731-1-drc@linux.vnet.ibm.com>



On 5/29/24 11:32 AM, David Christensen wrote:
> IBM POWER systems support more than one type of memory management unit
> (MMU).  The Power ISA 3.0 specification, which applies to P9 and later
> CPUs, defined a new Radix MMU which, among other things, allows an
> anonymous memory page mapping to be converted into a hugepage mapping
> at a specific address. This is a required feature in DPDK so we need
> to test the MMU type when POWER systems are used and provide a more
> useful error message for the user when running on an unsupported
> system such as P8/P9 on PowerVM.
> 
> All architectures other than ppc64le unconditionally report that the
> MMU is supported.  When running with ppc64le on Linux, the MMU is
> tested and the actual result is returned, while running with ppc64le
> on FreeBSD unconditionally reports that the MMU is supported to avoid
> unnecessary breakage until an actual test can be implemented for that
> environment (i.e. keeps existing behavior without the patch).
> 
> Bugzilla ID: 1221

Any chance I'll receive a review for this patch in this release cycle or 
should I go ahead and mark the Bugzilla as will not address?

Dave

      parent reply	other threads:[~2024-06-27 21:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 22:51 [PATCH] eal/linux: " David Christensen
2023-10-17 12:39 ` Thomas Monjalon
2023-10-23 21:59   ` David Christensen
2023-11-06 13:54     ` Thomas Monjalon
2023-10-23 23:19 ` [PATCH v2] eal/linux: " David Christensen
2023-10-24  2:02   ` David Christensen
2023-10-24 17:43   ` [PATCH v3] " David Christensen
2023-11-06 13:55     ` Thomas Monjalon
2023-11-30 19:18     ` [PATCH v4] eal: " David Christensen
2024-05-30 16:44       ` [PATCH v5] " David Christensen
2024-06-28 12:10         ` David Marchand
     [not found]       ` <20240529183222.105731-1-drc@linux.vnet.ibm.com>
2024-06-27 21:11         ` David Christensen [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=81a9db62-18db-4bbc-a27b-a941d9c55016@linux.ibm.com \
    --to=drc@linux.ibm.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=roretzla@linux.microsoft.com \
    --cc=ruifeng.wang@arm.com \
    --cc=stanislaw.kardach@gmail.com \
    --cc=thomas@monjalon.net \
    --cc=zhoumin@loongson.cn \
    /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).