From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] NVMe: Increase shutdown complete time
Date: Fri, 4 Apr 2014 09:33:02 -0600 (MDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1404040832460.4731@AMR> (raw)
In-Reply-To: <90064137F935C142B4B98BA318BB81A301DA531F@GREEN-CLEX.greenliant.com>
On Thu, 3 Apr 2014, Yung-Chin Chen wrote:
> Thanks, Keith, for your prompt response. I do not know Linux driver that
> well. If you use MODULE_PARM_DESC(), how do I specify the parameter for
> bootable NVMe device?
>
> For example, RedHat 7.0 has built-in NVMe driver and supports bootable
> from an NVMe device. The driver is buil-in to the kernel, and is not a
> loadable module. Where can I specify the parameters for built-in driver?
Okay, I'm not overly familiar with RHEL7, but I believe the following
is the way. If the module is built in, we can specify module parameters
at the vmlinuz line from the boot loader. To make it permanent, you
can append:
<module>.<module_param>=<value>
to the GRUB_CMDLINE_LINUX line in /etc/default/grub. The proposed new
parameter would look like 'nvme.nvme_io_timeout=20' if you want a 20
second timeout. After you set it, save the file, then run:
grub2-mkconfig --output=/boot/efi/EFI/redhat/grub.cfg
I assume you're efi booting since you mention booting from NVMe. If not
efi, the output would be in /boot/grub2/grub.cfg. The driver should then
use the new timeout value by default on each reboot after that.
next prev parent reply other threads:[~2014-04-04 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 16:24 [PATCH] NVMe: Increase shutdown complete time Keith Busch
2014-03-31 18:56 ` Dan McLeran
2014-03-31 20:37 ` Robles, Raymond C
2014-03-31 23:57 ` Dan McLeran
2014-04-03 22:55 ` Yung-Chin Chen
2014-04-03 23:12 ` Keith Busch
2014-04-04 0:18 ` Yung-Chin Chen
2014-04-04 15:33 ` Keith Busch [this message]
2014-04-04 3:23 ` Dan McLeran
2014-04-04 16:31 ` Matthew Wilcox
2014-04-04 15:22 ` Laura Jessen-SSI
2014-04-04 15:36 ` Keith Busch
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=alpine.LRH.2.03.1404040832460.4731@AMR \
--to=keith.busch@intel.com \
/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