On 8/6/19 5:56 PM, Matan Azrad wrote:
It may be needed by the user to limit the LRO session packet size.
In order to allow the above limitation, a new Rx configuration may be
added for the maximum LRO session size.

A new capability may be added too to expose the maximum LRO session size
supported by the port.

Signed-off-by: Matan Azrad <ma...@mellanox.com>
---
  doc/guides/rel_notes/deprecation.rst | 4 ++++
  1 file changed, 4 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst 
b/doc/guides/rel_notes/deprecation.rst
index 37b8592..c0cd9bc 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -59,6 +59,10 @@ Deprecation Notices
    Target release for removal of the legacy API will be defined once most
    PMDs have switched to rte_flow.
+* ethdev: new 32-bit fields may be added for maximum LRO session size, in
+  struct ``rte_eth_dev_info`` for the port capability and in struct
+  ``rte_eth_rxmode`` for the port configuration.
+
  * cryptodev: support for using IV with all sizes is added, J0 still can
    be used but only when IV length in following structs 
``rte_crypto_auth_xform``,
    ``rte_crypto_aead_xform`` is set to zero. When IV length is greater or equal



Acked-by: Andrew Rybchenko <arybche...@solarflare.com>

I don't know examples when the information is required, but can imagine.

Reply via email to