From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Jake Freeland <jfree@FreeBSD.org>,
Chenbo Xia <chenbox@nvidia.com>,
"Nipun Gupta" <nipun.gupta@amd.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH 2/4] bus/pci/bsd: Map resources at EAL baseaddr
Date: Thu, 8 May 2025 13:31:08 +0200 [thread overview]
Message-ID: <a149bcb6-44c0-479c-bb2b-907c8186557a@intel.com> (raw)
In-Reply-To: <20250506174046.1136711-3-jfree@FreeBSD.org>
On 5/6/2025 7:40 PM, Jake Freeland wrote:
> Provide the EAL base address as a hint to mmap(2), so device resources
> are not mapped where malloc(3) et al. make allocations.
>
> This makes mapping conflicts less likely for secondary processes that
> make memory allocations before initializing EAL.
>
> Signed-off-by: Jake Freeland <jfree@FreeBSD.org>
> ---
I remember attempting to fix this issue by reserving some amount of
address space for PCI devices in a similar way memory subsystem reserves
its address space. This doesn't quite do that but is as good a fix as it
can get without major rework IMO.
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2025-05-08 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 17:40 [PATCH 0/4] BSD PCI Fixes Jake Freeland
2025-05-06 17:40 ` [PATCH 1/4] bus/pci: Use force-noreplace flag when mapping PCI resources Jake Freeland
2025-05-08 11:32 ` Burakov, Anatoly
2025-05-06 17:40 ` [PATCH 2/4] bus/pci/bsd: Map resources at EAL baseaddr Jake Freeland
2025-05-08 11:31 ` Burakov, Anatoly [this message]
2025-05-06 17:40 ` [PATCH 3/4] bus/pci/bsd: Eliminate potential overflow Jake Freeland
2025-05-08 11:28 ` Burakov, Anatoly
2025-05-06 17:40 ` [PATCH 4/4] bus/pci/bsd: Fix device existence check Jake Freeland
2025-05-08 11:27 ` Burakov, Anatoly
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=a149bcb6-44c0-479c-bb2b-907c8186557a@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=jfree@FreeBSD.org \
--cc=nipun.gupta@amd.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).