From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [PATCH RFC 0/3] batman-adv: Enable support for jumbo frames
Date: Thu, 27 Jul 2023 10:13:41 +0200 [thread overview]
Message-ID: <20230727-jumbo-mtu-v1-0-036ce1a6e33c@narfation.org> (raw)
There are from time to time discussions about supporting jumbo frames
with batman-adv. While the changes were known since a longe time [1], no
actual tests were performed and no actual reviews were gathered.
Maybe some more interest can be stirred up by this RFC and some
Tested-by/Reviewed-by [2] can be collected - or some fixes.
[1] https://www.open-mesh.org/issues/365
[2] https://www.kernel.org/doc/html/v6.4/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes
Signed-off-by: Sven Eckelmann <sven@narfation.org>
---
Sven Eckelmann (3):
batman-adv: Avoid magic value for minimum MTU
batman-adv: Check hardif MTU against runtime MTU
batman-adv: Add support for jumbo frames
net/batman-adv/hard-interface.c | 24 ++++++++++++++----------
net/batman-adv/main.h | 2 ++
net/batman-adv/soft-interface.c | 5 +++--
3 files changed, 19 insertions(+), 12 deletions(-)
---
base-commit: f779cdaf7782ee765dbddd31f6d9a89abf0c52f9
change-id: 20230727-jumbo-mtu-13d736059c84
Best regards,
--
Sven Eckelmann <sven@narfation.org>
next reply other threads:[~2023-07-27 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 8:13 Sven Eckelmann [this message]
2023-07-27 8:13 ` [PATCH RFC 1/3] batman-adv: Avoid magic value for minimum MTU Sven Eckelmann
2023-07-27 8:13 ` [PATCH RFC 2/3] batman-adv: Check hardif MTU against runtime MTU Sven Eckelmann
2023-07-27 8:13 ` [PATCH RFC 3/3] batman-adv: Add support for jumbo frames Sven Eckelmann
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=20230727-jumbo-mtu-v1-0-036ce1a6e33c@narfation.org \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).