[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200102.153825.425008126689372806.davem@davemloft.net>
Date: Thu, 02 Jan 2020 15:38:25 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: brouer@...hat.com
Cc: netdev@...r.kernel.org, lirongqing@...du.com,
linyunsheng@...wei.com, ilias.apalodimas@...aro.org,
saeedm@...lanox.com, mhocko@...nel.org, peterz@...radead.org,
linux-kernel@...r.kernel.org
Subject: Re: [net-next v6 PATCH 0/2] page_pool: NUMA node handling fixes
From: Jesper Dangaard Brouer <brouer@...hat.com>
Date: Fri, 27 Dec 2019 18:13:13 +0100
> The recently added NUMA changes (merged for v5.5) to page_pool, it both
> contains a bug in handling NUMA_NO_NODE condition, and added code to
> the fast-path.
>
> This patchset fixes the bug and moves code out of fast-path. The first
> patch contains a fix that should be considered for 5.5. The second
> patch reduce code size and overhead in case CONFIG_NUMA is disabled.
>
> Currently the NUMA_NO_NODE setting bug only affects driver 'ti_cpsw'
> (drivers/net/ethernet/ti/), but after this patchset, we plan to move
> other drivers (netsec and mvneta) to use NUMA_NO_NODE setting.
Series applied to net-next with the "fallthrough" misspelling fixed in
patch #1.
Thank you.
Powered by blists - more mailing lists