Re: [PATCH net 6/6] iavf: cap advertised max_pkt_size at the single-buffer HW limit

[Alexander Lobakin <aleksander.lobakin@intel.com>]

From: Dave Butler <david.butler@appgate.com>
Date: Tue, 29 Sep 2026 20:32:53 +0000

>>> +     max_frame = min(max_frame, LIBIE_MAX_RX_BUF_LEN);
>> Shouldn't we cap it to 9728 instead?
> 
> No objection.  To be clear, LIBIE_MAX_RX_BUF_LEN is 9728, so it's
> the same value.

Oops sorry, I did misread. I thought for some reason that you now limit
it to (4096 - hr/tr overhead) >_<

Acked-by: Alexander Lobakin <aleksander.lobakin@intel.com>

> 
> Before 5fa4caff59f2 the cap was IAVF_MAX_RXBUFFER (9728, "largest size for
> single descriptor"), and that same commit replaced it with LIBIE_MAX_RX_BUF_LEN
> (9728U, "The largest size for a single descriptor as per HW").
> 
> That said, I'm happy to do whatever.  Just let me know your preference.
> 
> Intended recipient is public
> The information contained in this electronic mail is confidential information intended only for the use of the individual(s) or entity(s) named. If the reader of the message is not the addressee (or authorized to receive for the addressee), you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and/or by telephone and destroy the original message.

Thanks,
Olek