linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Juan Yescas <jyescas@google.com>,
	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>
Subject: Re: [LSF/MM/BPF TOPIC] CMA reservation optimizations
Date: Tue, 28 Jan 2025 10:58:41 +0100	[thread overview]
Message-ID: <50b7265e-64b9-41a3-af48-79ded6674f21@redhat.com> (raw)
In-Reply-To: <CAJDx_riGaT-2_6QWve9Dir56EYMZudtJ-0WAk5x+OwgTGshNNw@mail.gmail.com>

On 28.01.25 02:04, Juan Yescas wrote:
> 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.

I'm curious, here you say 4 MiB, above 8 MiB.

But nowadays it's usually 2 MiB (pageblock size), no?

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2025-01-28  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28  1:04 Juan Yescas
2025-01-28  9:58 ` David Hildenbrand [this message]
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=50b7265e-64b9-41a3-af48-79ded6674f21@redhat.com \
    --to=david@redhat.com \
    --cc=21cnbao@gmail.com \
    --cc=isaacmanjarres@google.com \
    --cc=jyescas@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