From: David Miller <davem@davemloft.net>
To: dmitry.krivoschekov@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] ipconfig tweaks
Date: Fri, 17 Apr 2009 03:45:12 -0700 (PDT) [thread overview]
Message-ID: <20090417.034512.40940557.davem@davemloft.net> (raw)
In-Reply-To: <49E85348.8080906@gmail.com>
From: Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>
Date: Fri, 17 Apr 2009 14:00:40 +0400
> Why don't let users to optimize boot-up time?
Because a generic scheme that works automatically is 1,000
times better than random kernel command line parms.
next prev parent reply other threads:[~2009-04-17 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 9:37 [PATCH 0/3] dmitry.krivoschekov
2009-04-16 9:37 ` [PATCH 1/3] ipconfig: use same time units for CONF_{PRE,POST}_OPEN delays dmitry.krivoschekov
2009-04-16 9:37 ` [PATCH 2/3] ipconfig: add 'ipwait' cmdline parameter dmitry.krivoschekov
2009-04-16 9:37 ` [PATCH 3/3] ipconfig: look for a network device forever if NFS root dmitry.krivoschekov
2009-04-17 8:23 ` [PATCH 0/3] David Miller
2009-04-17 10:00 ` [PATCH 0/3] ipconfig tweaks Dmitry Krivoschekov
2009-04-17 10:45 ` David Miller [this message]
2009-04-17 14:31 ` Benny Amorsen
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=20090417.034512.40940557.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dmitry.krivoschekov@gmail.com \
--cc=netdev@vger.kernel.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).