From: Jason Xing <kerneljasonxing@gmail.com>
To: jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, richardcochran@gmail.com, ast@kernel.org,
daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
alexandr.lobakin@intel.com
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH v2 net] ixgbe: allow to increase MTU to some extent with XDP enabled
Date: Mon, 30 Jan 2023 13:01:57 +0800 [thread overview]
Message-ID: <CAL+tcoCTH_yADMeQvpAV5FCgg+hEEW2NQNee7bHq92+NtN6oyg@mail.gmail.com> (raw)
In-Reply-To: <CAL+tcoCeBtiOeemuhQsTK8pnNLjmRRK7ukXLsiPt3YkOrJbYYA@mail.gmail.com>
On Fri, Jan 27, 2023 at 11:08 PM Jason Xing <kerneljasonxing@gmail.com> wrote:
>
> On Fri, Jan 27, 2023 at 10:54 PM Jason Xing <kerneljasonxing@gmail.com> wrote:
> >
> > My bad. It's not that right. Please ignore the v2 patch. I need some
> > time to do more studies and tests on this part.
> >
>
> In the meantime, any suggestions and help are appreciated :) I'm still
> working on it.
>
Dear maintainers, after several tests I did during this time as much
as possible, I couldn't find anything wrong though I am not that
familiar with the whole ixgbe code. I decided to 'reopen' this patch
v2. Please help me review the current patch.
Thanks,
Jason
>
> > Thanks,
> > Jason
> >
> > On Fri, Jan 27, 2023 at 8:20 PM Jason Xing <kerneljasonxing@gmail.com> wrote:
> > >
> > > From: Jason Xing <kernelxing@tencent.com>
> > >
> > > I encountered one case where I cannot increase the MTU size directly
> > > from 1500 to 2000 with XDP enabled if the server is equipped with
> > > IXGBE card, which happened on thousands of servers in production
> > > environment.
> > >
> > > This patch follows the behavior of changing MTU as i40e/ice does.
> > >
> > > Referrences:
> > > commit 23b44513c3e6f ("ice: allow 3k MTU for XDP")
> > > commit 0c8493d90b6bb ("i40e: add XDP support for pass and drop actions")
> > >
> > > Link: https://lore.kernel.org/lkml/20230121085521.9566-1-kerneljasonxing@gmail.com/
> > > Signed-off-by: Jason Xing <kernelxing@tencent.com>
> > > ---
> > > v2:
> > > 1) change the commit message.
> > > 2) modify the logic when changing MTU size suggested by Maciej and Alexander.
> > > ---
> > > drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 25 ++++++++++++-------
> > > 1 file changed, 16 insertions(+), 9 deletions(-)
> > >
> > > diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
> > > index ab8370c413f3..2c1b6eb60436 100644
> > > --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
> > > +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
> > > @@ -6777,6 +6777,18 @@ static void ixgbe_free_all_rx_resources(struct ixgbe_adapter *adapter)
> > > ixgbe_free_rx_resources(adapter->rx_ring[i]);
> > > }
> > >
> > > +/**
> > > + * ixgbe_max_xdp_frame_size - returns the maximum allowed frame size for XDP
> > > + * @adapter - device handle, pointer to adapter
> > > + */
> > > +static int ixgbe_max_xdp_frame_size(struct ixgbe_adapter *adapter)
> > > +{
> > > + if (PAGE_SIZE >= 8192 || adapter->flags2 & IXGBE_FLAG2_RX_LEGACY)
> > > + return IXGBE_RXBUFFER_2K;
> > > + else
> > > + return IXGBE_RXBUFFER_3K;
> > > +}
> > > +
> > > /**
> > > * ixgbe_change_mtu - Change the Maximum Transfer Unit
> > > * @netdev: network interface device structure
> > > @@ -6788,18 +6800,13 @@ static int ixgbe_change_mtu(struct net_device *netdev, int new_mtu)
> > > {
> > > struct ixgbe_adapter *adapter = netdev_priv(netdev);
> > >
> > > - if (adapter->xdp_prog) {
> > > + if (ixgbe_enabled_xdp_adapter(adapter)) {
> > > int new_frame_size = new_mtu + ETH_HLEN + ETH_FCS_LEN +
> > > VLAN_HLEN;
> > > - int i;
> > > -
> > > - for (i = 0; i < adapter->num_rx_queues; i++) {
> > > - struct ixgbe_ring *ring = adapter->rx_ring[i];
> > >
> > > - if (new_frame_size > ixgbe_rx_bufsz(ring)) {
> > > - e_warn(probe, "Requested MTU size is not supported with XDP\n");
> > > - return -EINVAL;
> > > - }
> > > + if (new_frame_size > ixgbe_max_xdp_frame_size(adapter)) {
> > > + e_warn(probe, "Requested MTU size is not supported with XDP\n");
> > > + return -EINVAL;
> > > }
> > > }
> > >
> > > --
> > > 2.37.3
> > >
next prev parent reply other threads:[~2023-01-30 5:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 12:20 [PATCH v2 net] ixgbe: allow to increase MTU to some extent with XDP enabled Jason Xing
2023-01-27 14:54 ` Jason Xing
2023-01-27 15:08 ` Jason Xing
2023-01-30 5:01 ` Jason Xing [this message]
2023-01-30 15:07 ` [Intel-wired-lan] " Maciej Fijalkowski
2023-01-31 3:00 ` Jason Xing
2023-01-31 11:07 ` Alexander Lobakin
2023-01-31 11:23 ` Jason Xing
2023-02-01 11:15 ` Alexander Lobakin
2023-02-01 13:28 ` Jason Xing
2023-02-02 13:11 ` Jason Xing
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=CAL+tcoCTH_yADMeQvpAV5FCgg+hEEW2NQNee7bHq92+NtN6oyg@mail.gmail.com \
--to=kerneljasonxing@gmail.com \
--cc=alexandr.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=john.fastabend@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).