From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: iommu@lists.linux-foundation.org,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Tariq Toukan" <tariqt@mellanox.com>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
"Robin Murphy" <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, brouer@redhat.com
Subject: Re: [PATCH] dma-mapping: bypass indirect calls for dma-direct
Date: Thu, 6 Dec 2018 18:40:27 +0100 [thread overview]
Message-ID: <20181206184027.291947c3@redhat.com> (raw)
In-Reply-To: <20181206153720.10702-2-hch@lst.de>
On Thu, 6 Dec 2018 07:37:20 -0800
Christoph Hellwig <hch@lst.de> wrote:
> Avoid expensive indirect calls in the fast path DMA mapping
> operations by directly calling the dma_direct_* ops if we are using
> the directly mapped DMA operations.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> include/linux/dma-direct.h | 17 -----
> include/linux/dma-mapping.h | 138 +++++++++++++++++++++++++++++++-----
> kernel/dma/direct.c | 13 ++--
> 3 files changed, 127 insertions(+), 41 deletions(-)
Hi Christoph,
Is this patch to be applied on top of the other (41) patches I just
tested with my XDP forward workload?
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2018-12-06 17:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 15:37 [RFC] avoid indirect calls for DMA direct mappings Christoph Hellwig
2018-12-06 15:37 ` Christoph Hellwig
[not found] ` <20181206153720.10702-1-hch-jcswGhMUV9g@public.gmane.org>
2018-12-06 15:37 ` [PATCH] dma-mapping: bypass indirect calls for dma-direct Christoph Hellwig
2018-12-06 15:37 ` Christoph Hellwig
2018-12-06 17:40 ` Jesper Dangaard Brouer [this message]
2018-12-06 18:35 ` Christoph Hellwig
2018-12-06 17:43 ` [RFC] avoid indirect calls for DMA direct mappings Jesper Dangaard Brouer
[not found] ` <20181206184351.4d9ece54-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-12-06 18:29 ` Nadav Amit
2018-12-06 18:29 ` Nadav Amit
[not found] ` <A9F9D621-445E-4F3C-95FE-3963A3DAEF98-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-12-06 18:45 ` Christoph Hellwig
2018-12-06 18:45 ` Christoph Hellwig
2018-12-06 18:28 ` Linus Torvalds
2018-12-06 18:30 ` Linus Torvalds
2018-12-06 18:43 ` Christoph Hellwig
2018-12-06 18:43 ` Christoph Hellwig
[not found] ` <20181206184330.GB30039-jcswGhMUV9g@public.gmane.org>
2018-12-06 18:51 ` Linus Torvalds
2018-12-06 18:51 ` Linus Torvalds
2018-12-06 18:54 ` Robin Murphy
2018-12-06 18:54 ` Robin Murphy
2018-12-06 20:00 ` Christoph Hellwig
2018-12-06 20:00 ` Christoph Hellwig
[not found] ` <20181206200006.GA31548-jcswGhMUV9g@public.gmane.org>
2018-12-06 20:24 ` Robin Murphy
2018-12-06 20:24 ` Robin Murphy
2018-12-07 1:21 ` Christoph Hellwig
2018-12-07 15:44 ` Jesper Dangaard Brouer
2018-12-07 15:44 ` Jesper Dangaard Brouer
2018-12-07 16:05 ` Jesper Dangaard Brouer
2018-12-07 16:05 ` Jesper Dangaard Brouer
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=20181206184027.291947c3@redhat.com \
--to=brouer@redhat.com \
--cc=hch@lst.de \
--cc=ilias.apalodimas@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=tariqt@mellanox.com \
--cc=toke@toke.dk \
--cc=torvalds@linux-foundation.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 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.