[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d4f10f4c0f1433bae658df8972a904f@baidu.com>
Date: Fri, 13 Dec 2019 06:27:28 +0000
From: "Li,Rongqing" <lirongqing@...du.com>
To: Yunsheng Lin <linyunsheng@...wei.com>,
Jesper Dangaard Brouer <brouer@...hat.com>
CC: Saeed Mahameed <saeedm@...lanox.com>,
"ilias.apalodimas@...aro.org" <ilias.apalodimas@...aro.org>,
"jonathan.lemon@...il.com" <jonathan.lemon@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"mhocko@...nel.org" <mhocko@...nel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Björn Töpel <bjorn.topel@...el.com>
Subject: 答复: [PATCH][v2] page_pool: handle page recycle for NUMA_NO_NODE condition
>
> It is good to allocate the rx page close to both cpu and device, but if
> both goal can not be reached, maybe we choose to allocate page that close
> to cpu?
>
I think it is true
If it is true, , we can remove pool->p.nid, and replace alloc_pages_node with
alloc_pages in __page_pool_alloc_pages_slow, and change pool_page_reusable as
that page_to_nid(page) is checked with numa_mem_id()
since alloc_pages hint to use the current node page, and __page_pool_alloc_pages_slow
will be called in NAPI polling often if recycle failed, after some cycle, the page will be from
local memory node.
-Li
Powered by blists - more mailing lists