All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Luiz Angelo Daros de Luca <luizluca@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: dsa: tag_rtl4_a: Bump min packet size
Date: Thu, 2 Nov 2023 12:31:23 +0200	[thread overview]
Message-ID: <20231102103123.hklqlsbb5kbq53mm@skbuf> (raw)
In-Reply-To: <CAJq09z6QwLNEc5rEGvE3jujZ-vb+vtUQLS-fkOnrdnYqk5KvxA@mail.gmail.com>

Hi Luiz,

On Wed, Nov 01, 2023 at 09:35:30AM -0300, Luiz Angelo Daros de Luca wrote:
> Hi Linus,
> 
> Sorry but I noticed no issues:
> 
> From the router:
> 
> No. Time Source Destination Protocol Length Info
> 1 0.000000000 192.168.1.1 192.168.1.2 ICMP 1514 Echo (ping) request id=0x0789, seq=23/5888, ttl=64 (reply in 2)
> 2 0.000040094 192.168.1.2 192.168.1.1 ICMP 1514 Echo (ping) reply id=0x0789, seq=23/5888, ttl=64 (request in 1)
> 
> From the host:
> 
> No. Time Source Destination Protocol Length Info
> 1 0.000000000 192.168.1.2 192.168.1.1 ICMP 1514 Echo (ping) request id=0x0002, seq=8/2048, ttl=64 (reply in 2)
> 2 0.000391800 192.168.1.1 192.168.1.2 ICMP 1514 Echo (ping) reply id=0x0002, seq=8/2048, ttl=64 (request in 1)
> 
> If I go over that limit, it fragments the packet as expected.

Could you run the shell command that sweeps over the entire range, fromhere?
https://lore.kernel.org/netdev/20231030222035.oqos7v7sdq5u6mti@skbuf/

  parent reply	other threads:[~2023-11-02 10:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  9:26 [PATCH net v2] net: dsa: tag_rtl4_a: Bump min packet size Linus Walleij
2023-10-30 14:16 ` Vladimir Oltean
2023-10-30 14:37   ` Linus Walleij
2023-10-30 15:23     ` Vladimir Oltean
2023-10-30 15:30       ` Vladimir Oltean
2023-10-31 21:22         ` Linus Walleij
2023-11-02 10:48           ` Vladimir Oltean
2023-10-30 21:50   ` Linus Walleij
2023-10-30 22:20     ` Vladimir Oltean
2023-10-30 22:57       ` Linus Walleij
2023-10-30 23:09         ` Vladimir Oltean
2023-10-30 23:11           ` Linus Walleij
2023-10-31  0:37           ` Andrew Lunn
2023-10-31  3:37             ` Florian Fainelli
2023-10-31 14:06             ` Linus Walleij
2023-10-31 16:23               ` Florian Fainelli
2023-10-30 23:33         ` Vladimir Oltean
2023-10-31 14:16           ` Linus Walleij
2023-10-31 16:34             ` Vladimir Oltean
2023-10-31 19:02               ` Linus Walleij
2023-11-02 12:32                 ` Vladimir Oltean
2023-10-31 19:18             ` Luiz Angelo Daros de Luca
2023-10-31 19:27               ` Linus Walleij
2023-11-01 12:35                 ` Luiz Angelo Daros de Luca
2023-11-01 20:26                   ` Linus Walleij
2023-11-02 10:04                     ` Vladimir Oltean
2023-11-02 10:45                     ` Vladimir Oltean
2023-11-03 17:05                     ` Luiz Angelo Daros de Luca
2023-12-30  5:19                     ` Luiz Angelo Daros de Luca
2023-12-30 12:28                       ` Linus Walleij
2023-12-30 23:56                         ` Luiz Angelo Daros de Luca
2023-11-02 10:31                   ` Vladimir Oltean [this message]
2023-11-03 17:13                     ` Luiz Angelo Daros de Luca
2023-10-31 22:44   ` Linus Walleij

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=20231102103123.hklqlsbb5kbq53mm@skbuf \
    --to=olteanv@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luizluca@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.