[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ca4a6cf9-6a8d-6fff-825d-b8311b3bce69@mellanox.com>
Date: Tue, 20 Mar 2018 10:18:02 +0200
From: Tariq Toukan <tariqt@...lanox.com>
To: Tariq Toukan <tariqt@...lanox.com>,
Jesper Dangaard Brouer <brouer@...hat.com>
Cc: netdev@...r.kernel.org,
BjörnTöpel <bjorn.topel@...el.com>,
magnus.karlsson@...el.com, eugenia@...lanox.com,
Jason Wang <jasowang@...hat.com>,
John Fastabend <john.fastabend@...il.com>,
Eran Ben Elisha <eranbe@...lanox.com>,
Saeed Mahameed <saeedm@...lanox.com>, galp@...lanox.com,
Daniel Borkmann <borkmann@...earbox.net>,
Alexei Starovoitov <alexei.starovoitov@...il.com>
Subject: Re: [bpf-next V3 PATCH 13/15] mlx5: use page_pool for
xdp_return_frame call
>> I see the issue. I have to go over the details in the driver, but I
>> think it should be sufficient to remove the WARN(). When the page_pool
>> was integrated with the MM-layer, being invoked from the put_page()
>> call itself, this would indicate a likely API misuse. But now, with
>> the page refcnt based recycle tricks, it is the norm (for non-XDP) that
>> put_page is called without the knowledge of page_pool.
>>
> I see, I'll remove the WARN and test.
>
Verified, it works. Please fix in next patchset.
Thanks.
Powered by blists - more mailing lists