Thread (2 messages) flat view 2 messages, 2 authors, 2017-03-22

Re: [PATCH net-next] cxgb4: Update IngPad and IngPack values

From: David Miller <davem@davemloft.net>
Date: 2017-03-22 17:54:06

From: Ganesh Goudar <redacted>
Date: Mon, 20 Mar 2017 14:22:38 +0530
From: Arjun Vynipadath <redacted>

We are using the smallest padding boundary (8 bytes), which isn't
smaller than the Memory Controller Read/Write Size

We get best performance in 100G when the Packing Boundary is a multiple
of the Maximum Payload Size. Its related to inefficient chopping of DMA
packets by PCIe, that causes more overhead on bus. So driver is helping
by making the starting address alignment to be MPS size.

We will try to determine PCIE MaxPayloadSize capabiltiy  and set
IngPackBoundary based on this value. If cache line size is greater than
MPS or determinig MPS fails, we will use cache line size to determine
IngPackBoundary(as before).

Signed-off-by: Arjun Vynipadath <redacted>
Signed-off-by: Casey Leedom <redacted>
Signed-off-by: Ganesh Goudar <redacted>
Applied, thank you.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help