[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140721091913.GD21375@breakpoint.cc>
Date: Mon, 21 Jul 2014 11:19:13 +0200
From: Florian Westphal <fw@...len.de>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Florian Westphal <fw@...len.de>,
David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
mst@...hat.com
Subject: Re: [PATCH -next] tun: stop tx queue when limit is hit
Eric Dumazet <eric.dumazet@...il.com> wrote:
> On Mon, 2014-07-21 at 10:31 +0200, Florian Westphal wrote:
> > Michael, do you think we could restore the 'stop queue' default
> > behaviour?
> >
> > Looking at your changelog, the only concern seems to be the
> > 'packets never consumed'/'receiver is stuck forever' case.
> >
> > What about reverting 5d097109257c03a7184, and then adding some
> > type of tun watchdog that will zap the rcv queue + tx queue wakeup?
> >
> > That should be quite noisy if we combine it with the WARN_ON
> > you usually get when (physical) NIC driver detect stalled tx unit.
> >
> > What do you think?
>
> Note that this patch had the ability to choose the behavior (drop or
> back pressure)
>
> http://patchwork.ozlabs.org/patch/338951/ ?
Eric, many thanks for this pointer. In fact, the related discussions
in v2 of the patchset (http://patchwork.ozlabs.org/patch/338803/)
also answers my questions above.
[ the concern is with applications that can get stuck just because
packet they sent is queued forever ]
I need to think about this some more, but in any case Michael outlined
a possible solution (limit queue delay) in the thread above.
Thanks,
Florian
--
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