> -----Original Message----- > From: Intel-wired-lan <intel-wired-lan-bounces@xxxxxxxxxx> On Behalf Of > Fabio M. De Francesco > Sent: Monday, July 4, 2022 7:31 PM > To: Brandeburg, Jesse <jesse.brandeburg@xxxxxxxxx>; Nguyen, Anthony L > <anthony.l.nguyen@xxxxxxxxx>; David S. Miller <davem@xxxxxxxxxxxxx>; > Eric Dumazet <edumazet@xxxxxxxxxx>; Jakub Kicinski <kuba@xxxxxxxxxx>; > Paolo Abeni <pabeni@xxxxxxxxxx>; Alexei Starovoitov <ast@xxxxxxxxxx>; > Daniel Borkmann <daniel@xxxxxxxxxxxxx>; Jesper Dangaard Brouer > <hawk@xxxxxxxxxx>; John Fastabend <john.fastabend@xxxxxxxxx>; intel- > wired-lan@xxxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx; linux- > kernel@xxxxxxxxxxxxxxx; bpf@xxxxxxxxxxxxxxx > Cc: Weiny, Ira <ira.weiny@xxxxxxxxx>; Fabio M. De Francesco > <fmdefrancesco@xxxxxxxxx> > Subject: [Intel-wired-lan] [PATCH] ixgbe: Don't call kmap() on page allocated > with GFP_ATOMIC > > Pages allocated with GFP_ATOMIC cannot come from Highmem. This is why > there is no need to call kmap() on them. > > Therefore, don't call kmap() on rx_buffer->page() and instead use a plain > page_address() to get the kernel address. > > Suggested-by: Ira Weiny <ira.weiny@xxxxxxxxx> > Suggested-by: Alexander Duyck <alexander.duyck@xxxxxxxxx> > Signed-off-by: Fabio M. De Francesco <fmdefrancesco@xxxxxxxxx> > --- > drivers/net/ethernet/intel/ixgbe/ixgbe_ethtool.c | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > Tested-by: Gurucharan <gurucharanx.g@xxxxxxxxx> (A Contingent worker at Intel)
