[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1460058531.13579.12.camel@netapp.com>
Date: Thu, 7 Apr 2016 19:48:50 +0000
From: "Waskiewicz, PJ" <PJ.Waskiewicz@...app.com>
To: "lsf@...ts.linux-foundation.org" <lsf@...ts.linux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"brouer@...hat.com" <brouer@...hat.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"bblanco@...mgrid.com" <bblanco@...mgrid.com>,
"alexei.starovoitov@...il.com" <alexei.starovoitov@...il.com>,
"James.Bottomley@...senPartnership.com"
<James.Bottomley@...senPartnership.com>,
"tom@...bertland.com" <tom@...bertland.com>,
"lsf-pc@...ts.linux-foundation.org"
<lsf-pc@...ts.linux-foundation.org>
Subject: Re: [Lsf] [LSF/MM TOPIC] Generic page-pool recycle facility?
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@...app.com
d: 503.961.3705
Powered by blists - more mailing lists