From: Kumar Gala <kumar.gala@freescale.com>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [RFC] Simple ioremap cache
Date: Mon, 7 Jun 2004 09:58:48 -0500 [thread overview]
Message-ID: <2E7C06A3-B893-11D8-92B4-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <20040605002915.GA17603@gate.ebshome.net>
> I have several questions on how we can enhance my simple hack so it
> can be
> acceptable into mainline:
>
> 0) Do we really need such stuff in mainline :) ?
I see no reason, its helpful for a number of embedded archs (4xx, 8xx,
e500)
> 1) Should this feature be enabled for all ppc32 archs or only for 4xx?
> I
> made ioremap profile for 2.6.6 kernel running on my G4 Powerbook and
> haven't noticed a lot of ioremap regions overlap (there was one
> instance where
> my patch would have helped if I've increased cache size to 32 entries).
This may be due to use of BATs on PPC Classic.
> 2) Should we cache allocation bigger than 4K? From Ebony and tipb
> profiles it
> doesn't seem advantogeous. Maybe other CPUs can benefit from the
> bigger sizes.
I think 4K is reasonable, I think this optimization is mainly for PPCs
w/ integrated periphs.
> 3) Should cache size (currently hardcoded to 10 entries) be made
> configurable?
Seems pointless to make it proper kernel config param. If someone
wants to change it they can always change the code themselves for there
purposes.
- kumar
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-07 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 0:29 [RFC] Simple ioremap cache Eugene Surovegin
2004-06-07 7:46 ` Marius Groeger
2004-06-07 8:48 ` Eugene Surovegin
2004-06-07 9:12 ` Marius Groeger
2004-06-07 9:26 ` Eugene Surovegin
2004-06-07 14:58 ` Kumar Gala [this message]
2004-06-07 15:27 ` Benjamin Herrenschmidt
2004-06-07 17:47 ` Kumar Gala
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=2E7C06A3-B893-11D8-92B4-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=ebs@ebshome.net \
--cc=linuxppc-dev@lists.linuxppc.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 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.