From: Christoph Hellwig <hch@infradead.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Benjamin Serebrin <serebrin@google.com>,
David Woodhouse <dwmw2@infradead.org>,
Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] iommu/vt-d: add NUMA awareness to intel_alloc_coherent()
Date: Wed, 1 Apr 2020 23:56:27 -0700 [thread overview]
Message-ID: <20200402065627.GA23242@infradead.org> (raw)
In-Reply-To: <34c70805-44f5-6697-3ebf-2f4d56779454@gmail.com>
On Wed, Apr 01, 2020 at 03:53:38PM -0700, Eric Dumazet wrote:
>
>
> On 2/2/18 10:59 AM, Eric Dumazet wrote:
> > On Fri, Feb 2, 2018 at 10:53 AM, Christoph Hellwig <hch@infradead.org> wrote:
> >> I've got patches pending to replace all that code with
> >> dma_direct_alloc, which will do the right thing. They were
> >> submitted for 4.16, and I will resend them after -rc1.
> >
> > I see, thanks Christoph !
> >
>
> Hi Christoph
>
> It seems 4.16 has shipped ( :) ) , and intel_alloc_coherent() still has no NUMA awareness.
Actually, that code went in and then got reverted again..
> Should I respin https://lore.kernel.org/patchwork/patch/884326/
Maybe. We are still hoping to convert intel-iommu to the dma-iommu
framework, but I'm not sure how long that is going to take, so maybe
just respin it for now.
prev parent reply other threads:[~2020-04-02 6:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 22:45 [PATCH] iommu/vt-d: add NUMA awareness to intel_alloc_coherent() Eric Dumazet
2018-02-01 1:46 ` Eric Dumazet
[not found] ` <1517438756.3715.108.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-01 6:33 ` [PATCH v2] " Eric Dumazet
2018-02-02 18:53 ` [PATCH] " Christoph Hellwig
2018-02-02 18:59 ` Eric Dumazet
2020-04-01 22:53 ` Eric Dumazet
2020-04-02 6:56 ` 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=20200402065627.GA23242@infradead.org \
--to=hch@infradead.org \
--cc=dwmw2@infradead.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=serebrin@google.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).