From: David Miller <davem@davemloft.net>
To: brouer@redhat.com
Cc: saeedm@dev.mellanox.co.il, tom@herbertland.com,
saeedm@mellanox.com, netdev@vger.kernel.org, tariqt@mellanox.com,
eric.dumazet@gmail.com
Subject: Re: [PATCH net] net/mlx5e: Do not recycle pages from emergency reserve
Date: Mon, 23 Jan 2017 10:45:40 -0500 (EST) [thread overview]
Message-ID: <20170123.104540.2005179027278796046.davem@davemloft.net> (raw)
In-Reply-To: <20170123093940.5d69539e@redhat.com>
From: Jesper Dangaard Brouer <brouer@redhat.com>
Date: Mon, 23 Jan 2017 09:39:40 +0100
> BUT there are other advantages of using a guaranteed recycle pool
> facility (like the page_pool). Namely, (1) DMA-overhead: keeping page
> DMA mapped to counter DMA+IOMMU overhead, (2) RX-zero-copy: opens up
> for a software memory model solution for pre-VMA-mapping pages to
> userspace (See: [1] for argument how this avoids leaking kernel mem,
> but only expose/leak packet-data mem)
+1
next prev parent reply other threads:[~2017-01-23 15:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 7:03 [PATCH net] net/mlx5e: Do not recycle pages from emergency reserve Eric Dumazet
2017-01-19 19:14 ` Saeed Mahameed
2017-01-19 19:25 ` Eric Dumazet
2017-01-19 19:39 ` Saeed Mahameed
2017-01-21 18:09 ` Tom Herbert
[not found] ` <CAPe+=50xs=MMqxHPgTiGa3qytL7633Cygf_vBWuAuq=ceLyacg@mail.gmail.com>
2017-01-21 19:26 ` Eric Dumazet
2017-01-23 9:14 ` Jesper Dangaard Brouer
2017-01-24 9:21 ` Saeed Mahameed
2017-01-21 20:31 ` Saeed Mahameed
2017-01-22 17:50 ` Tom Herbert
2017-01-24 9:29 ` Saeed Mahameed
2017-01-23 8:39 ` Jesper Dangaard Brouer
2017-01-23 15:45 ` David Miller [this message]
2017-01-22 18:09 ` Tom Herbert
2017-01-20 10:28 ` Saeed Mahameed
2017-01-20 17:43 ` David Miller
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=20170123.104540.2005179027278796046.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brouer@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@dev.mellanox.co.il \
--cc=saeedm@mellanox.com \
--cc=tariqt@mellanox.com \
--cc=tom@herbertland.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).