DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Ales Musil <amusil@redhat.com>,
	stable@dpdk.org,  Anatoly Burakov <anatoly.burakov@intel.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH] eal/linux: lower log level on allocation attempt failure
Date: Tue, 9 Jul 2024 10:57:28 +0200	[thread overview]
Message-ID: <CAJFAV8ynZk-e=s7kXx_srqvjMhaREdx-yVkBXcudXBtYeKpc9w@mail.gmail.com> (raw)
In-Reply-To: <20240626075959.6e27b59f@hermes.local>

On Wed, Jun 26, 2024 at 5:00 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> On Wed, 26 Jun 2024 16:51:42 +0200
> David Marchand <david.marchand@redhat.com> wrote:
>
> > On a ARM system with only 2MB hugepages configured, EAL emits an error
> > log with allocations larger than 512MB.
> >
> > Example with testpmd:
> > $ dpdk-testpmd --in-memory --no-pci --log-level=*:debug -- -i
> > ...
> > EAL: In-memory mode enabled, hugepages of size 33554432 bytes will be
> >       allocated anonymously
> > EAL: No free 32768 kB hugepages reported on node 0
> > EAL: In-memory mode enabled, hugepages of size 65536 bytes will be
> >       allocated anonymously
> > EAL: No free 64 kB hugepages reported on node 0
> > EAL: In-memory mode enabled, hugepages of size 1073741824 bytes will be
> >       allocated anonymously
> > EAL: No free 1048576 kB hugepages reported on node 0
> > ...
> > EAL: Detected memory type: socket_id:0 hugepage_sz:1073741824
> > EAL: Detected memory type: socket_id:0 hugepage_sz:33554432
> > EAL: Detected memory type: socket_id:0 hugepage_sz:2097152
> > EAL: Detected memory type: socket_id:0 hugepage_sz:65536
> > EAL: Creating 2 segment lists: n_segs:32 socket_id:0
> >       hugepage_sz:1073741824
> > ...
> > EAL: Creating 2 segment lists: n_segs:1024 socket_id:0
> >       hugepage_sz:33554432
> > ...
> > EAL: Creating 4 segment lists: n_segs:8192 socket_id:0
> >       hugepage_sz:2097152
> > ...
> > EAL: Creating 4 segment lists: n_segs:8192 socket_id:0
> >       hugepage_sz:65536
> > ...
> > EAL: Trying to obtain current memory policy.
> > EAL: Setting policy MPOL_PREFERRED for socket 0
> > EAL: alloc_seg(): mmap() failed: Cannot allocate memory
> > EAL: Ask a virtual area of 0x40000000 bytes
> > EAL: Virtual area found at 0x140000000 (size = 0x40000000)
> > EAL: attempted to allocate 2 segments, but only 0 were allocated
> > EAL: Restoring previous memory policy: 4
> > EAL: Trying to obtain current memory policy.
> > EAL: Setting policy MPOL_PREFERRED for socket 0
> > EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list
> > EAL: Restoring previous memory policy: 4
> > EAL: Trying to obtain current memory policy.
> > EAL: Setting policy MPOL_PREFERRED for socket 0
> > EAL: Restoring previous memory policy: 4
> > EAL: request: mp_malloc_sync
> > EAL: No shared files mode enabled, IPC is disabled
> > EAL: Heap on socket 0 was expanded by 1064MB
> > ...
> >
> > The reason is that the memzone allocation (~1GB large) would require
> > 17017 (32kB) segments. However, as displayed in the early logs, a 32kB
> > memory segment list can only host 8192 segments (controlled by the build
> > option RTE_MAX_MEMSEG_PER_LIST).
> >
> > This log message is misleading as there is no issue in the end: the
> > allocation succeeded with 2MB hugepages.
> >
> > Fixes: 582bed1e1d1d ("mem: support mapping hugepages at runtime")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>

Applied, thanks.


-- 
David Marchand


      reply	other threads:[~2024-07-09  8:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 14:51 David Marchand
2024-06-26 14:59 ` Stephen Hemminger
2024-07-09  8:57   ` David Marchand [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='CAJFAV8ynZk-e=s7kXx_srqvjMhaREdx-yVkBXcudXBtYeKpc9w@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=amusil@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@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).