From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: <linux-wireless@vger.kernel.org>, <ath10k@lists.infradead.org>
Subject: Re: [PATCH v2] ath10k: do not use coherent memory for allocated device memory chunks
Date: Tue, 8 Dec 2015 16:54:27 +0200 [thread overview]
Message-ID: <87si3d9ejg.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1448908321-3042-1-git-send-email-nbd@openwrt.org> (Felix Fietkau's message of "Mon, 30 Nov 2015 19:32:01 +0100")
Felix Fietkau <nbd@openwrt.org> writes:
> Coherent memory is more expensive to allocate (and constrained on some
> architectures where it has to be pre-allocated). It is also completely
> unnecessary, since the host has no reason to even access these allocated
> memory spaces
>
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Applied, thanks.
--
Kalle Valo
next prev parent reply other threads:[~2015-12-08 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 18:32 [PATCH v2] ath10k: do not use coherent memory for allocated device memory chunks Felix Fietkau
2015-12-08 14:54 ` Kalle Valo [this message]
2015-12-30 21:55 ` Ben Greear
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=87si3d9ejg.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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).