From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: l2x0: make background cache ops optional for clean and flush range
Date: Tue, 18 Sep 2012 07:50:04 -0500 [thread overview]
Message-ID: <50586DFC.9000902@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1209171827260.28681@xanadu.home>
On 09/17/2012 05:31 PM, Nicolas Pitre wrote:
> On Mon, 17 Sep 2012, Rob Herring wrote:
>
>> On 09/17/2012 02:47 PM, Russell King - ARM Linux wrote:
>>> Plus, because there's little justification behind this patch (apart
>>> from a vague reference to the speed of IO accesses) I'm going to say
>>> NAK to this until further information is forthcoming justifying this
>>> change.
>>>
>>
>> 30% faster network transmit rate with pktgen on highbank.
>
> Please always include your benchmark results in the patch description.
> That is highly valuable information when looking at commit logs.
>
Agreed as it would now be helpful if the original optimization to use
background ops had some data as well:
ARM: l2x0: Optimise the range based operations
For the big buffers which are in excess of cache size, the maintaince
operations by PA are very slow. For such buffers the maintainace
operations can be speeded up by using the WAY based method.
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Acked-by: Linus Walleij <linus.walleij@stericsson.com>
Rob
prev parent reply other threads:[~2012-09-18 12:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 19:45 [RFC PATCH] ARM: l2x0: avoid spinlock for sync op on pl310 Rob Herring
2012-09-10 23:13 ` Russell King - ARM Linux
2012-09-17 13:59 ` [PATCH v2] ARM: l2x0: make background cache ops optional for clean and flush range Rob Herring
2012-09-17 19:47 ` Russell King - ARM Linux
2012-09-17 20:29 ` Rob Herring
2012-09-17 20:45 ` Catalin Marinas
2012-09-17 21:36 ` Rob Herring
2012-09-17 21:47 ` Russell King - ARM Linux
2012-09-18 2:43 ` Rob Herring
2012-09-18 8:21 ` Catalin Marinas
2012-09-18 12:00 ` Rob Herring
2012-09-17 22:31 ` Nicolas Pitre
2012-09-18 12:50 ` Rob Herring [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=50586DFC.9000902@gmail.com \
--to=robherring2@gmail.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).