From: Jeremy Kerr <jk@ozlabs.org>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: aneesh.kumar@linux.vnet.ibm.com,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH 2/5] powerpc/cell: Drop support for 64K local store on 4K kernels
Date: Mon, 10 Aug 2015 16:14:09 +0800 [thread overview]
Message-ID: <55C85D51.5080903@ozlabs.org> (raw)
In-Reply-To: <1438928387-6454-2-git-send-email-mpe@ellerman.id.au>
Hi Michael,
> Back in the olden days we added support for using 64K pages to map the
> SPU (Synergistic Processing Unit) local store on Cell, when the main
> kernel was using 4K pages.
>
> This was useful at the time because distros were using 4K pages, but
> using 64K pages on the SPUs could reduce TLB pressure there.
>
> However these days the number of Cell users is approaching zero, and
> supporting this option adds unpleasant complexity to the memory
> management code.
>
> So drop the option, CONFIG_SPU_FS_64K_LS, and all related code.
Yep, I'd be happy to drop this - impact should be little to none.
Acked-by: Jeremy Kerr <jk@ozlabs.org>
Cheers,
Jeremy
next prev parent reply other threads:[~2015-08-10 8:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 6:19 [PATCH 1/5] powerpc/mm: Fix pte_pagesize_index() crash on 4K w/64K hash Michael Ellerman
2015-08-07 6:19 ` [PATCH 2/5] powerpc/cell: Drop support for 64K local store on 4K kernels Michael Ellerman
2015-08-10 8:14 ` Jeremy Kerr [this message]
2015-08-07 6:19 ` [PATCH 3/5] powerpc/mm: Drop the 64K on 4K version of pte_pagesize_index() Michael Ellerman
2015-08-10 5:34 ` Aneesh Kumar K.V
2015-08-07 6:19 ` [PATCH 4/5] powerpc/mm: Simplify page size kconfig dependencies Michael Ellerman
2015-08-10 5:36 ` Aneesh Kumar K.V
2015-08-07 6:19 ` [PATCH 5/5] powerpc/mm: Drop CONFIG_PPC_HAS_HASH_64K Michael Ellerman
2015-08-10 5:37 ` Aneesh Kumar K.V
2015-08-10 5:33 ` [PATCH 1/5] powerpc/mm: Fix pte_pagesize_index() crash on 4K w/64K hash Aneesh Kumar K.V
2015-08-19 23:14 ` [1/5] " Michael Ellerman
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=55C85D51.5080903@ozlabs.org \
--to=jk@ozlabs.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@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).