All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: "Måns Rullgård" <mans@mansr.com>
Cc: linux-omap@vger.kernel.org, Nishanth Menon <nm@ti.com>,
	tony@atomide.com, khilman@deeprootsystems.com,
	linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH 5/5] omap4: l2x0: Enable early BRESP bit
Date: Sat, 20 Nov 2010 15:38:42 +0530	[thread overview]
Message-ID: <fc42ca6f03504dea078f111b3ef03a4a@mail.gmail.com> (raw)
In-Reply-To: <yw1xfwux411g.fsf@unicorn.mansr.com>

> -----Original Message-----
> From: Måns Rullgård [mailto:mans@mansr.com]
> Sent: Saturday, November 20, 2010 12:02 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; nm@ti.com; mans@mansr.com;
> tony@atomide.com; khilman@deeprootsystems.com; linux-arm-
> kernel@lists.infradead.org
> Subject: Re: [PATCH 5/5] omap4: l2x0: Enable early BRESP bit
>
> Santosh Shilimkar <santosh.shilimkar@ti.com> writes:
>
> > The AXI protocol specifies that the write response can only
> > be sent back to an AXI master when the last write data has been
> > accepted. This optimization enables the PL310 to send the write
> > response of certain write transactions as soon as the store buffer
> > accepts the write address. This behavior is not compatible with
> > the AXI protocol and is disabled by default. You enable this
> > optimization by setting the Early BRESP Enable bit in the
> > Auxiliary Control Register (bit [30]).
>
> Did you measure the performance difference this makes, if any?
>
I didn't do any special runs for this bit alone. Just checked
with hardware team and they confirmed that you would gain a bit
on writes and it's good to enable it.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] omap4: l2x0: Enable early BRESP bit
Date: Sat, 20 Nov 2010 15:38:42 +0530	[thread overview]
Message-ID: <fc42ca6f03504dea078f111b3ef03a4a@mail.gmail.com> (raw)
In-Reply-To: <yw1xfwux411g.fsf@unicorn.mansr.com>

> -----Original Message-----
> From: M?ns Rullg?rd [mailto:mans at mansr.com]
> Sent: Saturday, November 20, 2010 12:02 AM
> To: Santosh Shilimkar
> Cc: linux-omap at vger.kernel.org; nm at ti.com; mans at mansr.com;
> tony at atomide.com; khilman at deeprootsystems.com; linux-arm-
> kernel at lists.infradead.org
> Subject: Re: [PATCH 5/5] omap4: l2x0: Enable early BRESP bit
>
> Santosh Shilimkar <santosh.shilimkar@ti.com> writes:
>
> > The AXI protocol specifies that the write response can only
> > be sent back to an AXI master when the last write data has been
> > accepted. This optimization enables the PL310 to send the write
> > response of certain write transactions as soon as the store buffer
> > accepts the write address. This behavior is not compatible with
> > the AXI protocol and is disabled by default. You enable this
> > optimization by setting the Early BRESP Enable bit in the
> > Auxiliary Control Register (bit [30]).
>
> Did you measure the performance difference this makes, if any?
>
I didn't do any special runs for this bit alone. Just checked
with hardware team and they confirmed that you would gain a bit
on writes and it's good to enable it.

  reply	other threads:[~2010-11-20 10:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 17:31 [PATCH 0/5] omap4: l2x0 fixes and cleanup Santosh Shilimkar
2010-11-19 17:31 ` Santosh Shilimkar
2010-11-19 17:31 ` [PATCH 1/5] ARM: l2x0: Add aux control register bitfields Santosh Shilimkar
2010-11-19 17:31   ` Santosh Shilimkar
2010-11-19 17:31   ` [PATCH 2/5] omap4: l2x0: Construct the AUXCTRL value using defines Santosh Shilimkar
2010-11-19 17:31     ` Santosh Shilimkar
2010-11-19 17:31     ` [PATCH 3/5] omap4: l2x0: enable instruction and data prefetching Santosh Shilimkar
2010-11-19 17:31       ` Santosh Shilimkar
2010-11-19 17:31       ` [PATCH 4/5] omap4: l2x0: Set share override bit Santosh Shilimkar
2010-11-19 17:31         ` Santosh Shilimkar
2010-11-19 17:31         ` [PATCH 5/5] omap4: l2x0: Enable early BRESP bit Santosh Shilimkar
2010-11-19 17:31           ` Santosh Shilimkar
2010-11-19 18:32           ` Måns Rullgård
2010-11-19 18:32             ` Måns Rullgård
2010-11-20 10:08             ` Santosh Shilimkar [this message]
2010-11-20 10:08               ` Santosh Shilimkar
2010-11-22 20:11     ` [PATCH 2/5] omap4: l2x0: Construct the AUXCTRL value using defines Kevin Hilman
2010-11-22 20:11       ` Kevin Hilman
2010-11-22 20:21       ` Måns Rullgård
2010-11-22 20:21         ` Måns Rullgård
2010-11-19 18:13   ` [PATCH 1/5] ARM: l2x0: Add aux control register bitfields Catalin Marinas
2010-11-19 18:13     ` Catalin Marinas
2010-12-02 11:57 ` [PATCH 0/5] omap4: l2x0 fixes and cleanup Santosh Shilimkar
2010-12-02 11:57   ` Santosh Shilimkar
2010-12-14  5:08   ` Santosh Shilimkar
2010-12-14  5:08     ` Santosh Shilimkar
2010-12-18 17:39     ` Tony Lindgren
2010-12-18 17:39       ` Tony Lindgren

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=fc42ca6f03504dea078f111b3ef03a4a@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mans@mansr.com \
    --cc=nm@ti.com \
    --cc=tony@atomide.com \
    /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.