From: "Waskiewicz, PJ" <PJ.Waskiewicz@netapp.com>
To: "lsf@lists.linux-foundation.org" <lsf@lists.linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"brouer@redhat.com" <brouer@redhat.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bblanco@plumgrid.com" <bblanco@plumgrid.com>,
"alexei.starovoitov@gmail.com" <alexei.starovoitov@gmail.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"tom@herbertland.com" <tom@herbertland.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>
Subject: Re: [Lsf] [LSF/MM TOPIC] Generic page-pool recycle facility?
Date: Thu, 7 Apr 2016 19:48:50 +0000 [thread overview]
Message-ID: <1460058531.13579.12.camel@netapp.com> (raw)
In-Reply-To: <20160407161715.52635cac@redhat.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 951 bytes --]
On Thu, 2016-04-07 at 16:17 +0200, Jesper Dangaard Brouer wrote:
> (Topic proposal for MM-summit)
>
> Network Interface Cards (NIC) drivers, and increasing speeds stress
> the page-allocator (and DMA APIs).  A number of driver specific
> open-coded approaches exists that work-around these bottlenecks in
> the
> page allocator and DMA APIs. E.g. open-coded recycle mechanisms, and
> allocating larger pages and handing-out page "fragments".
>
> I'm proposing a generic page-pool recycle facility, that can cover
> the
> driver use-cases, increase performance and open up for zero-copy RX.
Is this based on the page recycle stuff from ixgbe that used to be in
the driver? Â If so I'd really like to be part of the discussion.
-PJ
--
PJ Waskiewicz
Principal Engineer, NetApp
e: pj.waskiewicz@netapp.com
d: 503.961.3705
N§²æìr¸zǧu©²Æ {\béì¹»\x1c®&Þ)îÆi¢Ø^nr¶Ý¢j$½§$¢¸\x05¢¹¨è§~'.)îÄÃ,yèm¶ÿÃ\f%{±j+ðèצj)Z·
WARNING: multiple messages have this Message-ID (diff)
From: "Waskiewicz, PJ" <PJ.Waskiewicz@netapp.com>
To: "lsf@lists.linux-foundation.org" <lsf@lists.linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"brouer@redhat.com" <brouer@redhat.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bblanco@plumgrid.com" <bblanco@plumgrid.com>,
"alexei.starovoitov@gmail.com" <alexei.starovoitov@gmail.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"tom@herbertland.com" <tom@herbertland.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>
Subject: Re: [Lsf] [LSF/MM TOPIC] Generic page-pool recycle facility?
Date: Thu, 7 Apr 2016 19:48:50 +0000 [thread overview]
Message-ID: <1460058531.13579.12.camel@netapp.com> (raw)
In-Reply-To: <20160407161715.52635cac@redhat.com>
On Thu, 2016-04-07 at 16:17 +0200, Jesper Dangaard Brouer wrote:
> (Topic proposal for MM-summit)
>
> Network Interface Cards (NIC) drivers, and increasing speeds stress
> the page-allocator (and DMA APIs). A number of driver specific
> open-coded approaches exists that work-around these bottlenecks in
> the
> page allocator and DMA APIs. E.g. open-coded recycle mechanisms, and
> allocating larger pages and handing-out page "fragments".
>
> I'm proposing a generic page-pool recycle facility, that can cover
> the
> driver use-cases, increase performance and open up for zero-copy RX.
Is this based on the page recycle stuff from ixgbe that used to be in
the driver? If so I'd really like to be part of the discussion.
-PJ
--
PJ Waskiewicz
Principal Engineer, NetApp
e: pj.waskiewicz@netapp.com
d: 503.961.3705
next prev parent reply other threads:[~2016-04-07 19:53 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1460034425.20949.7.camel@HansenPartnership.com>
2016-04-07 14:17 ` [LSF/MM TOPIC] Generic page-pool recycle facility? Jesper Dangaard Brouer
2016-04-07 14:38 ` [Lsf-pc] " Christoph Hellwig
2016-04-07 15:11 ` [Lsf] " Bart Van Assche
2016-04-10 18:45 ` Sagi Grimberg
2016-04-11 21:41 ` Jesper Dangaard Brouer
2016-04-11 22:02 ` Alexander Duyck
2016-04-11 22:02 ` Alexander Duyck
2016-04-12 6:28 ` Jesper Dangaard Brouer
2016-04-12 15:37 ` Alexander Duyck
2016-04-12 15:37 ` Alexander Duyck
2016-04-11 22:21 ` Alexei Starovoitov
2016-04-12 6:16 ` Jesper Dangaard Brouer
2016-04-12 17:20 ` Alexei Starovoitov
2016-04-07 15:48 ` Chuck Lever
2016-04-07 16:14 ` [Lsf-pc] [Lsf] " Rik van Riel
2016-04-07 19:43 ` [Lsf] [Lsf-pc] " Jesper Dangaard Brouer
2016-04-07 15:18 ` Eric Dumazet
2016-04-07 15:18 ` Eric Dumazet
2016-04-09 9:11 ` [Lsf] " Jesper Dangaard Brouer
2016-04-09 12:34 ` Eric Dumazet
2016-04-11 20:23 ` Jesper Dangaard Brouer
2016-04-11 21:27 ` Eric Dumazet
2016-04-11 21:27 ` Eric Dumazet
2016-04-07 19:48 ` Waskiewicz, PJ [this message]
2016-04-07 19:48 ` Waskiewicz, PJ
2016-04-07 20:38 ` Jesper Dangaard Brouer
2016-04-08 16:12 ` Alexander Duyck
2016-04-11 8:58 ` [Lsf-pc] " Mel Gorman
2016-04-11 12:26 ` Jesper Dangaard Brouer
2016-04-11 13:08 ` Mel Gorman
2016-04-11 16:19 ` [Lsf] " Jesper Dangaard Brouer
2016-04-11 16:19 ` Jesper Dangaard Brouer
2016-04-11 16:53 ` Eric Dumazet
2016-04-11 19:47 ` Jesper Dangaard Brouer
2016-04-11 21:14 ` Eric Dumazet
2016-04-11 18:07 ` Mel Gorman
2016-04-11 19:26 ` Jesper Dangaard Brouer
2016-04-11 16:20 ` Matthew Wilcox
2016-04-11 17:46 ` Thadeu Lima de Souza Cascardo
2016-04-11 17:46 ` Thadeu Lima de Souza Cascardo
2016-04-11 18:37 ` Jesper Dangaard Brouer
2016-04-11 18:37 ` Jesper Dangaard Brouer
2016-04-11 18:53 ` Bart Van Assche
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=1460058531.13579.12.camel@netapp.com \
--to=pj.waskiewicz@netapp.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bblanco@plumgrid.com \
--cc=brouer@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=lsf@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.