From: Jacob Keller <jacob.e.keller@intel.com>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Dave Ertman <david.m.ertman@intel.com>,
Michal Kubiak <michal.kubiak@intel.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH net] ice: fix VF queue configuration with low MTU values
Date: Tue, 7 Apr 2026 15:50:32 -0700 [thread overview]
Message-ID: <88c37486-70aa-4109-a5b1-ee74cce23bc5@intel.com> (raw)
In-Reply-To: <20260406145641.1020623-1-jtornosm@redhat.com>
On 4/6/2026 7:56 AM, Jose Ignacio Tornos Martinez wrote:
> The ice driver's VF queue configuration validation rejects
> databuffer_size values below 1024 bytes, which prevents VFs from
> using MTU values below 871 bytes.
>
> The iavf driver calculates databuffer_size based on the MTU using:
> databuffer_size = ALIGN(MTU + LIBETH_RX_LL_LEN, 128)
>
> where LIBETH_RX_LL_LEN = 26 (ETH_HLEN + 2*VLAN_HLEN + ETH_FCS_LEN).
>
> For MTU values below 871:
> MTU 870: 870 + 26 = 896, aligned to 128 = 896 (< 1024, rejected)
> MTU 871: 871 + 26 = 897, aligned to 128 = 1024 (>= 1024, accepted)
>
> The 1024-byte minimum seems unnecessarily restrictive, because the hardware
> supports databuffer_size as low as 128 bytes (the alignment boundary),
> which should allow MTU values down to the standard minimum of 68 bytes.
>
> I haven't found the reason why the limit was configured in the commit
> 9c7dd7566d18 ("ice: add validation in OP_CONFIG_VSI_QUEUES VF message"), so
> with no more information and since it is working, change the minimum
> databuffer_size validation from 1024 to 128 bytes to allow standard low
> MTU values while still preventing invalid configurations.
>
I dug through some of our internal history and found that there was no
justification on why 1024 was chosen.
I agree with your assessment that the value of 128 makes the most sense
as it is the actual hardware minimum. I wonder if we used to always use
data buffer sizes of 1024 before the conversion to libeth. Either way, I
think it makes sense to allow smaller buffers since the modern iAVF will
request them.
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
> Fixes: 9c7dd7566d18 ("ice: add validation in OP_CONFIG_VSI_QUEUES VF message")
> cc: stable@vger.kernel.org
> Signed-off-by: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
> ---
> drivers/net/ethernet/intel/ice/virt/queues.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/ice/virt/queues.c b/drivers/net/ethernet/intel/ice/virt/queues.c
> index f73d5a3e83d4..31be2f76181c 100644
> --- a/drivers/net/ethernet/intel/ice/virt/queues.c
> +++ b/drivers/net/ethernet/intel/ice/virt/queues.c
> @@ -840,7 +840,7 @@ int ice_vc_cfg_qs_msg(struct ice_vf *vf, u8 *msg)
>
> if (qpi->rxq.databuffer_size != 0 &&
> (qpi->rxq.databuffer_size > ((16 * 1024) - 128) ||
> - qpi->rxq.databuffer_size < 1024))
> + qpi->rxq.databuffer_size < 128))
> goto error_param;
>
> ring->rx_buf_len = qpi->rxq.databuffer_size;
next prev parent reply other threads:[~2026-04-07 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 14:56 [PATCH net] ice: fix VF queue configuration with low MTU values Jose Ignacio Tornos Martinez
2026-04-07 22:50 ` Jacob Keller [this message]
2026-04-08 5:42 ` [Intel-wired-lan] " Michal Swiatkowski
2026-04-08 6:24 ` Paul Menzel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88c37486-70aa-4109-a5b1-ee74cce23bc5@intel.com \
--to=jacob.e.keller@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jtornosm@redhat.com \
--cc=kuba@kernel.org \
--cc=michal.kubiak@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox