[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20161213.145333.514056260418695987.davem@davemloft.net>
Date: Tue, 13 Dec 2016 14:53:33 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: john.fastabend@...il.com
Cc: brouer@...hat.com, cl@...ux.com, rppt@...ux.vnet.ibm.com,
netdev@...r.kernel.org, linux-mm@...ck.org,
willemdebruijn.kernel@...il.com, bjorn.topel@...el.com,
magnus.karlsson@...el.com, alexander.duyck@...il.com,
mgorman@...hsingularity.net, tom@...bertland.com,
bblanco@...mgrid.com, tariqt@...lanox.com, saeedm@...lanox.com,
jesse.brandeburg@...el.com, METH@...ibm.com, vyasevich@...il.com
Subject: Re: Designing a safe RX-zero-copy Memory Model for Networking
From: John Fastabend <john.fastabend@...il.com>
Date: Tue, 13 Dec 2016 09:43:59 -0800
> What does "zero-copy send packet-pages to the application/socket that
> requested this" mean? At the moment on x86 page-flipping appears to be
> more expensive than memcpy (I can post some data shortly) and shared
> memory was proposed and rejected for security reasons when we were
> working on bifurcated driver.
The whole idea is that we map all the active RX ring pages into
userspace from the start.
And just how Jesper's page pool work will avoid DMA map/unmap,
it will also avoid changing the userspace mapping of the pages
as well.
Thus avoiding the TLB/VM overhead altogether.
Powered by blists - more mailing lists