[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20191120083955.4c3dc7149a33518e9594293a@suse.de>
Date: Wed, 20 Nov 2019 08:39:55 +0100
From: Thomas Bogendoerfer <tbogendoerfer@...e.de>
To: David Miller <davem@...emloft.net>
Cc: corbet@....net, kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH net-next] net: ipconfig: Make device wait timeout
configurable
On Tue, 19 Nov 2019 18:44:46 -0800 (PST)
David Miller <davem@...emloft.net> wrote:
> From: Thomas Bogendoerfer <tbogendoerfer@...e.de>
> Date: Tue, 19 Nov 2019 13:06:46 +0100
>
> > If network device drivers are using deferred probing it's possible
> > that waiting for devices to show up in ipconfig is already over,
> > when the device eventually shows up. With the new netdev_max_wait
> > kernel cmdline pataremter it's now possible to extend this time.
> >
> > Signed-off-by: Thomas Bogendoerfer <tbogendoerfer@...e.de>
>
> This is one of those "user's shouldn't have to figure this crap out"
> situations.
>
> To me, a knob is always a step backwards, and makes Linux harder to
> use.
>
> The irony in all of this, is that the kernel knows when this stuff is
> happening. So the ipconfig code should be taught that drivers are
> still plugging themselves together and probing, instead of setting
> some arbitrary timeout to wait for these things to occur.
fine with, I'll have a look how to solve it taht way.
Thomas.
--
SUSE Software Solutions Germany GmbH
HRB 36809 (AG Nürnberg)
Geschäftsführer: Felix Imendörffer
Powered by blists - more mailing lists