linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org, Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [RFC PATCH] powerpc/64s: CONFIG_PPC_HASH_MMU
Date: Fri, 20 Mar 2020 12:00:13 +1000	[thread overview]
Message-ID: <1584667943.t0isihrd3v.astroid@bobo.none> (raw)
In-Reply-To: <878sjxdlpa.fsf@mpe.ellerman.id.au>

Michael Ellerman's on March 19, 2020 2:15 pm:
> Nicholas Piggin <npiggin@gmail.com> writes:
>> This allows the 64s hash MMU code to be compiled out if radix is
>> selected. This saves about 128kB kernel image size (90kB text) on
>> powernv_defconfig minus KVM, 40kB on a tiny config.
> 
> TBH my feelings are:
>  - the size savings don't excite me much, given our kernels can be ~32MB
>    in size.
>  - it's unlikely a major (or any) distro would ever enable this, so it
>    would not be well tested.

Yeah, it would only really be used for firmware or certain embedded 
things. We'd want some actual user before it's merged.

>  - it adds a *lot* of #ifdefs.

Yeah I started to get lazy, we can improve those quite a bit I think.

> So if we want to get this merged I'd want a good amount of refactoring
> done to avoid the bulk of the #ifdefs in the code. ie. lots of wrapper
> inlines etc. to hide the #ifdefs.
> 
> And someone to put up their hand to maintain it, ie. ensure it keeps
> building and fix any issues that come up when it breaks.

Yeah, I'll keep tinkering on it, it might come in useful.

Thanks,
Nick

      reply	other threads:[~2020-03-20  2:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02  4:49 [RFC PATCH] powerpc/64s: CONFIG_PPC_HASH_MMU Nicholas Piggin
2020-03-19  4:15 ` Michael Ellerman
2020-03-20  2:00   ` Nicholas Piggin [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=1584667943.t0isihrd3v.astroid@bobo.none \
    --to=npiggin@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).