From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
npiggin@gmail.com, benh@kernel.crashing.org, paulus@samba.org,
mpe@ellerman.id.au
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH] powerpc/mm: Reduce memory usage for mm_context_t for radix
Date: Tue, 2 Apr 2019 21:12:03 +0530 [thread overview]
Message-ID: <200e5a1a-9475-8d43-666c-1845f9d95d1b@linux.ibm.com> (raw)
In-Reply-To: <80f34a0e-2bbe-8751-6571-3f844103fc37@c-s.fr>
On 4/2/19 9:06 PM, Christophe Leroy wrote:
>
>
> Le 02/04/2019 à 16:34, Aneesh Kumar K.V a écrit :
>> Currently, our mm_context_t on book3s64 include all hash specific
>> context details like slice mask, subpage protection details. We
>> can skip allocating those on radix. This will help us to save
>> 8K per mm_context with radix translation.
>>
>> With the patch applied we have
>>
>> sizeof(mm_context_t) = 136
>> sizeof(struct hash_mm_context) = 8288
>>
>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
>> ---
>> NOTE:
>>
>> If we want to do this, I am still trying to figure out how best we can
>> do this
>> without all the #ifdef and other overhead for 8xx book3e
>
> Did you have a look at my series
> https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=98170 ?
>
> It tries to reduce as much as feasible the #ifdefs and stuff.
>
>
Not yet. But a cursory look tell me introducing hash_mm_context
complicates this further unless I introduce something similar for nohash
32? Are you ok with that?
-aneesh
next prev parent reply other threads:[~2019-04-02 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 14:34 [RFC PATCH] powerpc/mm: Reduce memory usage for mm_context_t for radix Aneesh Kumar K.V
2019-04-02 15:36 ` Christophe Leroy
2019-04-02 15:42 ` Aneesh Kumar K.V [this message]
2019-04-02 18:34 ` Christophe Leroy
2019-04-02 18:31 ` Christophe Leroy
2019-04-02 18:37 ` Christophe Leroy
2019-04-04 16:13 ` Nicholas Piggin
2019-04-04 16:55 ` Christophe Leroy
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=200e5a1a-9475-8d43-666c-1845f9d95d1b@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.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).