[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190107105342.GA31296@apalos>
Date:   Mon, 7 Jan 2019 12:53:42 +0200
From:   Ilias Apalodimas <ilias.apalodimas@...aro.org>
To:     Ioana Ciocoi Radulescu <ruxandra.radulescu@....com>
Cc:     Jesper Dangaard Brouer <brouer@...hat.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "davem@...emloft.net" <davem@...emloft.net>,
        Ioana Ciornei <ioana.ciornei@....com>,
        "dsahern@...il.com" <dsahern@...il.com>,
        Camelia Alexandra Groza <camelia.groza@....com>
Subject: Re: Explaining the XDP page-requirement (Was: [PATCH v2 net-next
 0/8] dpaa2-eth: Introduce XDP support)
Hi Ioana,
> > > Thanks a lot, that's great info, especially for someone who hasn't followed
> > > so closely xdp development from its beginning.
> > >
> > > I'll look into updating the dpaa2-eth driver to use one page per frame and
> > > see how that goes.
> > 
> > If you have time, we can discuss merging whatever hardware features are
> > not
> > supported in the page_pool API and use that to allocate pages?
> 
> Sure. I'd like to first transition to plain page allocations instead of
> napi_alloc_frag() and validate that's ok (I've been meaning to try that for
> a while now but haven't got around to it yet), and then we can explore
> how that might be integrated in page_pool.
Great, ping us if you need anything
Thanks
/Ilias
Powered by blists - more mailing lists
 
