From: Thomas Bogendoerfer <tbogendoerfer@suse.de>
To: David Miller <davem@davemloft.net>
Cc: corbet@lwn.net, kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: ipconfig: Make device wait timeout configurable
Date: Wed, 20 Nov 2019 08:39:55 +0100 [thread overview]
Message-ID: <20191120083955.4c3dc7149a33518e9594293a@suse.de> (raw)
In-Reply-To: <20191119.184446.1007728375771623470.davem@davemloft.net>
On Tue, 19 Nov 2019 18:44:46 -0800 (PST)
David Miller <davem@davemloft.net> wrote:
> From: Thomas Bogendoerfer <tbogendoerfer@suse.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@suse.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
prev parent reply other threads:[~2019-11-20 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 12:06 Thomas Bogendoerfer
2019-11-20 2:44 ` David Miller
2019-11-20 7:39 ` Thomas Bogendoerfer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191120083955.4c3dc7149a33518e9594293a@suse.de \
--to=tbogendoerfer@suse.de \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®