From: Eric Dumazet <eric.dumazet@gmail.com>
To: Sergey Matyukevich <geomatsi@gmail.com>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
sergey.matyukevich.os@quantenna.com
Subject: Re: question: ip forwarding and fq/mq qdisc
Date: Fri, 14 Dec 2018 05:06:47 -0800 [thread overview]
Message-ID: <c3ac480b-2c6c-689a-a39e-75df601e5261@gmail.com> (raw)
In-Reply-To: <20181214120210.kmeuwvajuiwlp2n7@bars>
On 12/14/2018 04:02 AM, Sergey Matyukevich wrote:
> Hi all,
>
> I have been running 4.18-rc8 kernel with enabled IP forwarding between
> wired and wireless interfaces, where both interfaces
> were configured as fq qdisc.
>
> However after moving to 4.20-rc1 kernel the same configuration does not
> work anymore: pass-through packets are not forwarded in both directions.
> Forwarding starts working again only if I change qdisc of _both_ interfaces
> to anything but fq/mq. For instance any combination of pfifo/fq_codel/noqueue
> works fine.
>
> Does it look like a regression or it is a known change in behavior ?
>
> Regards,
> Sergey
>
Hi Sergey
I guess EDT model broke this use case.
I was under the impression skb->tstamp was cleared when forwarding packets, maybe I was wrong.
Can you try the following ?
diff --git a/net/ipv4/ip_forward.c b/net/ipv4/ip_forward.c
index 06ee4696703c0ce72ea914403b739839e60f1584..00ec819f949b5e76ea96be901a697f4e12d5cf4d 100644
--- a/net/ipv4/ip_forward.c
+++ b/net/ipv4/ip_forward.c
@@ -79,6 +79,7 @@ static int ip_forward_finish(struct net *net, struct sock *sk, struct sk_buff *s
if (unlikely(opt->optlen))
ip_forward_options(skb);
+ skb->tstamp = 0;
return dst_output(net, sk, skb);
}
next prev parent reply other threads:[~2018-12-14 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 12:02 question: ip forwarding and fq/mq qdisc Sergey Matyukevich
2018-12-14 13:06 ` Eric Dumazet [this message]
2018-12-14 14:12 ` Sergey Matyukevich
2018-12-14 14:21 ` Eric Dumazet
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=c3ac480b-2c6c-689a-a39e-75df601e5261@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=geomatsi@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergey.matyukevich.os@quantenna.com \
--cc=xiyou.wangcong@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