linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tbogendoerfer@suse.de>
To: Jonathan Corbet <corbet@lwn.net>,
	"David S. Miller" <davem@davemloft.net>,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: [PATCH net-next] net: ipconfig: Make device wait timeout configurable
Date: Tue, 19 Nov 2019 13:06:46 +0100	[thread overview]
Message-ID: <20191119120647.31547-1-tbogendoerfer@suse.de> (raw)

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>
---
 Documentation/admin-guide/kernel-parameters.txt |  5 +++++
 net/ipv4/ipconfig.c                             | 22 +++++++++++++++++++---
 2 files changed, 24 insertions(+), 3 deletions(-)

diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index a84a83f8881e..6083ac04f075 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -2755,6 +2755,11 @@
 			This usage is only documented in each driver source
 			file if at all.
 
+	netdev_max_wait=
+			[IP_PNP] set the maximum time in seconds to wait
+			for net devices showing up, when doing kernel
+			IP configuration
+
 	nf_conntrack.acct=
 			[NETFILTER] Enable connection tracking flow accounting
 			0 to disable accounting
diff --git a/net/ipv4/ipconfig.c b/net/ipv4/ipconfig.c
index 9bcca08efec9..851ea8239f5f 100644
--- a/net/ipv4/ipconfig.c
+++ b/net/ipv4/ipconfig.c
@@ -103,6 +103,9 @@
 /* Wait for carrier timeout default in seconds */
 static unsigned int carrier_timeout = 120;
 
+/* Wait for devices to show up in seconds */
+static unsigned int device_max_wait = 12;
+
 /*
  * Public IP configuration
  */
@@ -1402,13 +1405,11 @@ __be32 __init root_nfs_parse_addr(char *name)
 	return addr;
 }
 
-#define DEVICE_WAIT_MAX		12 /* 12 seconds */
-
 static int __init wait_for_devices(void)
 {
 	int i;
 
-	for (i = 0; i < DEVICE_WAIT_MAX; i++) {
+	for (i = 0; i < device_max_wait; i++) {
 		struct net_device *dev;
 		int found = 0;
 
@@ -1797,3 +1798,18 @@ static int __init set_carrier_timeout(char *str)
 	return 1;
 }
 __setup("carrier_timeout=", set_carrier_timeout);
+
+static int __init set_device_max_wait(char *str)
+{
+	ssize_t ret;
+
+	if (!str)
+		return 0;
+
+	ret = kstrtouint(str, 0, &device_max_wait);
+	if (ret)
+		return 0;
+
+	return 1;
+}
+__setup("netdev_max_wait=", set_device_max_wait);
-- 
2.16.4


             reply	other threads:[~2019-11-19 12:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 12:06 Thomas Bogendoerfer [this message]
2019-11-20  2:44 ` [PATCH net-next] net: ipconfig: Make device wait timeout configurable David Miller
2019-11-20  7:39   ` Thomas Bogendoerfer

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=20191119120647.31547-1-tbogendoerfer@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;
as well as URLs for NNTP newsgroup(s).