linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gking@nvidia.com (Gary King)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Add support for page alloc w/ custom cache attributes
Date: Mon,  2 Aug 2010 19:42:45 -0700	[thread overview]
Message-ID: <1280803369-13362-1-git-send-email-gking@nvidia.com> (raw)

This series is an attempt to address the recent discussion regarding
dual-mapping of kernel pages with different cache attributes that
was spawned by the VCM patch series (and other IOMMU / SMMU patches),
to allow memory allocations for the SMMU to use any kernel-managed
page.

This adds 2 new APIs (enabled with the ARM_ATTRIB_ALLOCATOR config)
to allocate and free pages with caller-specified cache attributes.
When this config is enabled, the kernel's lowmem mapping is mapped
using PTEs rather than sections, so that the cache attributes for the
kernel's mapping can be updated when the page is allocated to match
the caller's request (and returned to pgprot_kernel when freed).

Additionally, this patch stack adds an additional memory type (inner-
writeback, outer-non-cacheable) that we (NVIDIA) have found to be
extremely beneficial in optimizing the drawing that Android's window
system (among others) uses.

I'm sending this out for comments on the overall direction. The APIs
are similar to functions that we implemented in the Tegra system MMU
driver.

- Gary

             reply	other threads:[~2010-08-03  2:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03  2:42 Gary King [this message]
2010-08-03  2:42 ` [PATCH 1/4] [ARM] mmu: add option to map lowmem with page mappings Gary King
2010-08-03  2:42 ` [PATCH 2/4] [ARM] mm: add page allocator for customizing cache attributes Gary King
2010-08-03  2:42 ` [PATCH 3/4] [ARM] mm: add memory type for inner-writeback Gary King
2010-08-03  7:41   ` Russell King - ARM Linux
2010-08-03 15:24     ` Gary King
2010-08-03  2:42 ` [PATCH 4/4] [ARM] dma-mapping: add support for inner-writeback pages Gary King

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=1280803369-13362-1-git-send-email-gking@nvidia.com \
    --to=gking@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.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).