Searched hist:"4 f4542bfb3b539bef118578ffafcc98e4ce91979" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/drivers/net/ethernet/intel/ixgbe/ |
| H A D | ixgbe.h | diff 4f4542bfb3b539bef118578ffafcc98e4ce91979 Tue Jan 17 10:36:14 CST 2017 Alexander Duyck <alexander.h.duyck@intel.com> ixgbe: Make use of order 1 pages and 3K buffers independent of FCoE
In order to support build_skb with jumbo frames it will be necessary to use
3K buffers for the Rx path with 8K pages backing them. This is needed on
architectures that implement 4K pages because we can't support 2K buffers
plus padding in a 4K page.
In the case of systems that support page sizes larger than 4K the 3K
attribute will only be applied to FCoE as we can fall back to using just 2K
buffers and adding the padding.
Signed-off-by: Alexander Duyck <alexander.h.duyck@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
|
| H A D | ixgbe_main.c | diff 4f4542bfb3b539bef118578ffafcc98e4ce91979 Tue Jan 17 10:36:14 CST 2017 Alexander Duyck <alexander.h.duyck@intel.com> ixgbe: Make use of order 1 pages and 3K buffers independent of FCoE
In order to support build_skb with jumbo frames it will be necessary to use
3K buffers for the Rx path with 8K pages backing them. This is needed on
architectures that implement 4K pages because we can't support 2K buffers
plus padding in a 4K page.
In the case of systems that support page sizes larger than 4K the 3K
attribute will only be applied to FCoE as we can fall back to using just 2K
buffers and adding the padding.
Signed-off-by: Alexander Duyck <alexander.h.duyck@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
|