linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Juan Yescas <jyescas@google.com>
To: lsf-pc@lists.linux-foundation.org,
	Suren Baghdasaryan <surenb@google.com>,
	 linux-mm@kvack.org, Kalesh Singh <kaleshsingh@google.com>,
	 Isaac Manjarres <isaacmanjarres@google.com>,
	"T.J. Mercier" <tjmercier@google.com>,  Zi Yan <ziy@nvidia.com>,
	Barry Song <21cnbao@gmail.com>,
	David Hildenbrand <david@redhat.com>
Subject: [LSF/MM/BPF TOPIC] CMA reservation optimizations
Date: Mon, 27 Jan 2025 17:04:38 -0800	[thread overview]
Message-ID: <CAJDx_riGaT-2_6QWve9Dir56EYMZudtJ-0WAk5x+OwgTGshNNw@mail.gmail.com> (raw)

Hi LSF organizers,

I would like to continue discussing this topic with the mm community:

"CMA reservation optimizations"

Note: There is already an email in the linux-mm mailing list that is
discussing this issue. The title is:

"CMA reservations require 32MiB alignment in 16KiB page size kernels
instead of 8MiB in 4KiB page size kernel"

Background

When the drivers reserve CMA memory in 16KiB kernels, the minimum
alignment is 32 MiB as per CMA_MIN_ALIGNMENT_BYTES. However, in 4KiB
kernels, the CMA alignment is 4MiB.

This is forcing the drivers to reserve more memory than required in
16KiB kernels,
even if they only require 4MiB or 8MiB.

reserved-memory {
      #address-cells = <2>;
      #size-cells = <2>;
      ranges;
      tpu_cma_reserve: tpu_cma_reserve {
            compatible = "shared-dma-pool";
            reusable;
           size = <0x0 0x2000000>; /* 32 MiB */
}

Thanks
Juan


             reply	other threads:[~2025-01-28  1:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28  1:04 Juan Yescas [this message]
2025-01-28  9:58 ` David Hildenbrand
2025-01-28 17:07   ` Juan Yescas
2025-01-28 18:33     ` David Hildenbrand
2025-01-28 20:15       ` Zi Yan
2025-04-02 18:01         ` Juan Yescas

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=CAJDx_riGaT-2_6QWve9Dir56EYMZudtJ-0WAk5x+OwgTGshNNw@mail.gmail.com \
    --to=jyescas@google.com \
    --cc=21cnbao@gmail.com \
    --cc=david@redhat.com \
    --cc=isaacmanjarres@google.com \
    --cc=kaleshsingh@google.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=surenb@google.com \
    --cc=tjmercier@google.com \
    --cc=ziy@nvidia.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