From: Andrew Lunn <andrew@lunn.ch>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Sven Van Asbroeck <thesven73@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Bryan Whitehead <bryan.whitehead@microchip.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
David S Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v1 2/2] lan743x: boost performance: limit PCIe bandwidth requirement
Date: Wed, 9 Dec 2020 02:22:18 +0100 [thread overview]
Message-ID: <20201209012218.GN2475764@lunn.ch> (raw)
In-Reply-To: <3aed88da-8e82-3bd0-6822-d30f1bd5ec9e@gmail.com>
> dma_sync_single_for_{cpu,device} is what you would need in order to make
> a partial cache line invalidation. You would still need to unmap the
> same address+length pair that was used for the initial mapping otherwise
> the DMA-API debugging will rightfully complain.
But often you don't unmap it, you call dma_sync_single_for_device and
put it back into the ring.
Andrew
next prev parent reply other threads:[~2020-12-09 1:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 3:44 [PATCH net v1 1/2] lan743x: improve performance: fix rx_napi_poll/interrupt ping-pong Sven Van Asbroeck
2020-12-06 3:44 ` [PATCH net v1 2/2] lan743x: boost performance: limit PCIe bandwidth requirement Sven Van Asbroeck
2020-12-08 19:43 ` Jakub Kicinski
2020-12-08 21:54 ` Sven Van Asbroeck
2020-12-08 22:51 ` Andrew Lunn
2020-12-08 23:02 ` Sven Van Asbroeck
2020-12-08 23:07 ` Jakub Kicinski
2020-12-08 23:36 ` Florian Fainelli
2020-12-09 1:22 ` Andrew Lunn [this message]
2020-12-09 3:49 ` Sven Van Asbroeck
2020-12-09 14:09 ` Andrew Lunn
2020-12-17 0:57 ` Sven Van Asbroeck
2020-12-17 1:01 ` Florian Fainelli
2020-12-17 3:18 ` Sven Van Asbroeck
2020-12-08 23:13 ` Jakub Kicinski
2020-12-08 19:50 ` [PATCH net v1 1/2] lan743x: improve performance: fix rx_napi_poll/interrupt ping-pong Jakub Kicinski
2020-12-08 22:23 ` Sven Van Asbroeck
2020-12-08 23:29 ` Jakub Kicinski
2020-12-08 23:50 ` Eric Dumazet
2020-12-09 0:17 ` Sven Van Asbroeck
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=20201209012218.GN2475764@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=thesven73@gmail.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
Powered by JetHome