From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Jonas Pfefferle1 <JPF@zurich.ibm.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [kernel, v2] powerpc/powernv/ioda: Remove explicit max window size check
Date: Tue, 14 Nov 2017 22:12:14 +1100 (AEDT) [thread overview]
Message-ID: <3yblG653bTz9sPr@ozlabs.org> (raw)
In-Reply-To: <20171107034301.35120-1-aik@ozlabs.ru>
On Tue, 2017-11-07 at 03:43:01 UTC, Alexey Kardashevskiy wrote:
> DMA windows can only have a size of power of two on IODA2 hardware and
> using memory_hotplug_max() to determine the upper limit won't work
> correcly if it returns not power of two value.
>
> This removes the check as the platform code does this check in
> pnv_pci_ioda2_setup_default_config() anyway; the other client is VFIO
> and that thing checks against locked_vm limit which prevents the userspace
> from locking too much memory.
>
> It is expected to impact DPDK on machines with non-power-of-two RAM size,
> mostly. KVM guests are less likely to be affected as usually guests get
> less than half of hosts RAM.
>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/9003a249815a15704f415954039d1c
cheers
prev parent reply other threads:[~2017-11-14 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 3:43 [PATCH kernel v2] powerpc/powernv/ioda: Remove explicit max window size check Alexey Kardashevskiy
2017-11-13 23:52 ` David Gibson
2017-11-14 11:12 ` Michael Ellerman [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=3yblG653bTz9sPr@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=JPF@zurich.ibm.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.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).