[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 12 Dec 2013 20:00:42 +0100
From: Hannes Frederic Sowa <hannes@...essinduktion.org>
To: David Miller <davem@...emloft.net>
Cc: vyasevich@...il.com, dvlasenk@...hat.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, kuznet@....inr.ac.ru,
jmorris@...ei.org, yoshfuji@...ux-ipv6.org, kaber@...sh.net,
jpirko@...hat.com
Subject: Re: [patch net-next v2] ipv6: log autoconfiguration failures
On Thu, Dec 12, 2013 at 01:24:41PM -0500, David Miller wrote:
> From: Vlad Yasevich <vyasevich@...il.com>
> Date: Thu, 12 Dec 2013 12:58:18 -0500
>
> > On 12/12/2013 12:22 PM, David Miller wrote:
> >> Give it statistics just like we have for every other kind of similar
> >> event.
> >
> > The fact that link-local address could not be generated for a specific
> > device type does not lend itself well to counting. There is no way
> > from to tell from the counter which device does not support IPv6 autoconfig.
>
> If the statistic is per-device, which I recommended it be implemented as,
> you indeed can.
>
> And I do not buy the argument that this is "useless" because the admin
> is just going to kill the interface and create a new one. When you
> notice there is a problem, you look at the statistics before doing
> that!
Granted.
IMHO both ways are fine with a slight opionion to counters being overkill. ;)
--
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