From: Felix Kaechele <felix@kaechele.ca>
To: Sven Eckelmann <sven@narfation.org>, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH] batman-adv: Don't skb_split skbuffs with frag_list
Date: Sat, 16 Apr 2022 10:01:25 -0400 [thread overview]
Message-ID: <bf02aeff-210c-a5e0-47d7-c5b276c9b794@kaechele.ca> (raw)
In-Reply-To: <20220416122434.33061-1-sven@narfation.org>
Hi there,
initial testing shows that this patch seems to fix the issue.
We are currently at 30 minutes of uptime on our fairly busy mesh which
is already 15-30 times better than before.
Thanks for the super quick turnaround on this one, especially on easter
weekend.
I will report back after some more uptime, but I have a feeling that if
it is working right now it will probably continue to function just fine.
Thanks again!
Regards,
Felix
next prev parent reply other threads:[~2022-04-16 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 12:24 [PATCH] batman-adv: Don't skb_split skbuffs with frag_list Sven Eckelmann
2022-04-16 14:01 ` Felix Kaechele [this message]
2022-04-16 14:21 ` Andrew Lunn
2022-04-16 17:17 ` Sven Eckelmann
2022-04-16 17:26 ` Andrew Lunn
[not found] ` <165011769041.26690.10778801125078465694@diktynna.open-mesh.org>
2022-04-17 16:07 ` Felix Kaechele
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=bf02aeff-210c-a5e0-47d7-c5b276c9b794@kaechele.ca \
--to=felix@kaechele.ca \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.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).