netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Antoine Tenart <antoine.tenart@bootlin.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Brian Brooks <brian.brooks@linaro.org>,
	David Miller <davem@davemloft.net>,
	maxime.chevallier@bootlin.com, ymarkman@marvell.com,
	stefanc@marvell.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, bjorn.topel@intel.com,
	brian.brooks@arm.com
Subject: Re: [PATCH] net: mvpp2: avoid bouncing buffers
Date: Mon, 11 Mar 2019 08:46:55 -0700	[thread overview]
Message-ID: <20190311154655.GB28982@infradead.org> (raw)
In-Reply-To: <20190301142602.GC3554@kwain>

On Fri, Mar 01, 2019 at 03:26:02PM +0100, Antoine Tenart wrote:
> Hi Christoph,
> 
> I saw you sent this patch as part of another series back in August, but
> it seems it was never applied and I can't find it even in -next. We made
> some tests and this patch is helping a lot the PPv2 engine driver in
> improving its performances.
> 
> Do you plan on re-sending it, or reworking it? Are there current issues
> with it that prevent it from being merged upstream? Can we help in any
> way?

Hi Antoine,

it's been a while, but my vague memory is that this caused failures
in some ARM setups, and I was tought why for AMBA setting up the
default mask is a bad idea.  I don't really remember more, though.

      reply	other threads:[~2019-03-11 15:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20  2:47 [PATCH] net: mvpp2: avoid bouncing buffers Brian Brooks
2018-08-20  2:55 ` David Miller
2018-08-20  6:23   ` Christoph Hellwig
2018-08-20  7:02     ` Yan Markman
2018-08-27 13:55     ` Brian Brooks
2018-08-27 15:48       ` Christoph Hellwig
2018-09-02  2:10         ` Brian Brooks
2019-03-01 14:26         ` Antoine Tenart
2019-03-11 15:46           ` Christoph Hellwig [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=20190311154655.GB28982@infradead.org \
    --to=hch@infradead.org \
    --cc=antoine.tenart@bootlin.com \
    --cc=bjorn.topel@intel.com \
    --cc=brian.brooks@arm.com \
    --cc=brian.brooks@linaro.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=stefanc@marvell.com \
    --cc=ymarkman@marvell.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 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).