[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1416927193.29427.12.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Tue, 25 Nov 2014 06:53:13 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Yang Yingliang <yangyingliang@...wei.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net
Subject: Re: [PATCH net-next 3/3] sch_fq: segment too big GSO packets
On Tue, 2014-11-25 at 21:24 +0800, Yang Yingliang wrote:
> If a GSO packet cost more than 125ms to send, segment the
> packet and send individual segments.
>
> Signed-off-by: Yang Yingliang <yangyingliang@...wei.com>
> ---
> net/sched/sch_fq.c | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/net/sched/sch_fq.c b/net/sched/sch_fq.c
> index ec6eff8..0119340 100644
> --- a/net/sched/sch_fq.c
> +++ b/net/sched/sch_fq.c
> @@ -423,6 +423,30 @@ static int fq_enqueue(struct sk_buff *skb, struct Qdisc *sch)
> return qdisc_drop(skb, sch);
> }
>
I am opposed to this patch serie.
FQ is used at 40Gb speeds at Google, we can not afford doing such copies
in FQ at all.
If you believe packets are too big at this point, then you should fix
the provider of such packets.
Sorry.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists