From: "Björn Töpel" <bjorn.topel@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Maxim Mikityanskiy <maximmi@mellanox.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, bpf <bpf@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Karlsson, Magnus" <magnus.karlsson@intel.com>
Subject: Re: the XSK buffer pool needs be to reverted
Date: Fri, 26 Jun 2020 14:45:49 +0200 [thread overview]
Message-ID: <f049b82a-4c69-c021-8988-78d757169247@intel.com> (raw)
In-Reply-To: <20200626124104.GA8835@lst.de>
On 2020-06-26 14:41, Christoph Hellwig wrote:
> On Fri, Jun 26, 2020 at 02:22:41PM +0200, Björn Töpel wrote:
[...]
>>
>> Understood. Wdyt about something in the lines of the diff below? It's
>> build tested only, but removes all non-dma API usage ("poking
>> internals"). Would that be a way forward, and then as a next step work
>> on a solution that would give similar benefits, but something that would
>> live in the dma mapping core?
>
> Yes, that would solve the immediate issues.
>
Good. I'll cook a proper patch and post it.
Björn
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-06-26 12:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 7:47 the XSK buffer pool needs be to reverted Christoph Hellwig
2020-06-26 12:22 ` Björn Töpel
2020-06-26 12:41 ` Christoph Hellwig
2020-06-26 12:45 ` Björn Töpel [this message]
2020-06-26 20:54 ` Jonathan Lemon
2020-06-27 7:02 ` Christoph Hellwig
2020-06-29 13:15 ` Robin Murphy
2020-06-30 19:08 ` Jonathan Lemon
2020-07-01 9:46 ` Robin Murphy
2020-07-06 19:59 ` Jonathan Lemon
2020-07-07 17:35 ` Robin Murphy
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=f049b82a-4c69-c021-8988-78d757169247@intel.com \
--to=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=maximmi@mellanox.com \
--cc=netdev@vger.kernel.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).