All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Avnish Chouhan <avnish@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: brking@linux.ibm.com, meghanaprakash@in.ibm.com,
	sourabhjain@linux.ibm.com, maddy@linux.ibm.com,
	Avnish Chouhan <avnish@linux.ibm.com>
Subject: Re: [PATCH v2] powerpc: increase MIN RMA size for CAS negotiation
Date: Sat, 07 Dec 2024 12:58:00 +1100	[thread overview]
Message-ID: <87ser05k5z.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20241206065545.14815-1-avnish@linux.ibm.com>

Avnish Chouhan <avnish@linux.ibm.com> writes:
> Change RMA size from 512 MB to 768 MB which will result 
> in more RMA at boot time for PowerPC.

Did you consider just increasing it to 1GB?

It's possible there's some folks running LPARs with less than 1GB, but
they are unlikely to continue doing so by the time this change trickles
into distros. To be supported modern RHEL requires 2GB minimum RAM
anyway.

Can you also describe the behaviour users will see when they configure
an LPAR with less than 768MB of RAM.

cheers


  reply	other threads:[~2024-12-07  1:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06  6:55 [PATCH v2] powerpc: increase MIN RMA size for CAS negotiation Avnish Chouhan
2024-12-07  1:58 ` Michael Ellerman [this message]
2024-12-11 12:05   ` Avnish Chouhan
2025-01-09  9:32   ` Sourabh Jain
2025-01-22 12:43 ` Madhavan Srinivasan
2025-01-23  3:06   ` Sourabh Jain
2025-01-24  3:58   ` Sourabh Jain
  -- strict thread matches above, loose matches on Subject: below --
2025-03-03 16:49 Avnish Chouhan
2025-03-04 15:09 ` Daniel Kiper
2025-03-07  9:01   ` Avnish Chouhan
2025-03-10 13:12     ` Daniel Kiper
2025-03-11  9:29       ` Avnish Chouhan
2025-03-11 13:44         ` Daniel Kiper
2025-03-12  9:46           ` Avnish Chouhan

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=87ser05k5z.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=avnish@linux.ibm.com \
    --cc=brking@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=meghanaprakash@in.ibm.com \
    --cc=sourabhjain@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.