From: Christoph Hellwig <hch@lst.de>
To: Nadav Amit <nadav.amit@gmail.com>
Cc: "Jesper Dangaard Brouer" <brouer@redhat.com>,
"Christoph Hellwig" <hch@lst.de>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
iommu <iommu@lists.linux-foundation.org>,
"Robin Murphy" <robin.murphy@arm.com>,
"Tariq Toukan" <tariqt@mellanox.com>,
"Josh Poimboeuf" <jpoimboe@redhat.com>
Subject: Re: [RFC] avoid indirect calls for DMA direct mappings
Date: Thu, 6 Dec 2018 19:45:33 +0100 [thread overview]
Message-ID: <20181206184533.GC30039@lst.de> (raw)
In-Reply-To: <A9F9D621-445E-4F3C-95FE-3963A3DAEF98@gmail.com>
On Thu, Dec 06, 2018 at 10:29:35AM -0800, Nadav Amit wrote:
> Did you happen to see my RFC for "automatic" indirect call promotion?
>
> https://lkml.org/lkml/2018/10/18/175
>
> I hope to get v1 based on Josh responses next week.
I'll take a look when you repost it. Although I'm always a little vary
of under the hood magic like this..
next prev parent reply other threads:[~2018-12-06 18:45 UTC|newest]
Thread overview: 17+ 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 ` [PATCH] dma-mapping: bypass indirect calls for dma-direct Christoph Hellwig
2018-12-06 17:40 ` Jesper Dangaard Brouer
2018-12-06 18:35 ` Christoph Hellwig
2018-12-06 17:43 ` [RFC] avoid indirect calls for DMA direct mappings Jesper Dangaard Brouer
2018-12-06 18:29 ` Nadav Amit
2018-12-06 18:45 ` Christoph Hellwig [this message]
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:51 ` Linus Torvalds
2018-12-06 18:54 ` Robin Murphy
2018-12-06 20:00 ` Christoph Hellwig
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 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=20181206184533.GC30039@lst.de \
--to=hch@lst.de \
--cc=brouer@redhat.com \
--cc=ilias.apalodimas@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nadav.amit@gmail.com \
--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 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).