netdev
[Top] [All Lists]

Re: 2.6.7-rc3: unregister_netdevice: waiting for tun0 to become free. Us

To: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Subject: Re: 2.6.7-rc3: unregister_netdevice: waiting for tun0 to become free. Usage count = 1
From: "David S. Miller" <davem@xxxxxxxxxx>
Date: Sun, 13 Jun 2004 21:43:55 -0700
Cc: schwab@xxxxxxx, netdev@xxxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx
In-reply-to: <20040614044717.GA28929@gondor.apana.org.au>
References: <20040613121514.6b3c1c8a.davem@redhat.com> <E1BZeW1-0008Ny-00@gondolin.me.apana.org.au> <20040613234142.GA32329@gondor.apana.org.au> <20040613183622.3a814506.davem@redhat.com> <20040614015013.GA11048@gondor.apana.org.au> <20040613210725.70dbd016.davem@redhat.com> <20040614042216.GA28669@gondor.apana.org.au> <20040613212708.1903d54c.davem@redhat.com> <20040614044240.GA28844@gondor.apana.org.au> <20040614044717.GA28929@gondor.apana.org.au>
Sender: netdev-bounce@xxxxxxxxxxx
On Mon, 14 Jun 2004 14:47:17 +1000
Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote:

> And there's more :) The work done in ifdown also falls in the same
> category.  Its work will be carried out in the GC anyway.
> 
> Actually in all these cases it could take a lot more than two minutes
> if there is a long-living entity (maybe a TCP connection) holding onto
> the dst.  So I guess #1 and #2 should be addressed at some point.

Maybe the solution is to initiate a GC run as soon as possible
instead of however long into the future it would have ended
up running.

Wouldn't that help?

<Prev in Thread] Current Thread [Next in Thread>