LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 07-16-2010, 05:29 PM   #1
kopper27
Member
 
Registered: Nov 2009
Posts: 147

Rep: Reputation: 16
noop option kernel


hi guys

I have Suse 10 and Suse 11 and I need to add the option elevator=noop

Code:
Suse 11
kernel /boot/vmlinuz-2.6.27.29-0.1-pae root=/dev/sda1 resume=/dev/sda2 splash=silent showopts vga=0x32b elevator=noop
Code:
Suse 10
kernel /boot/vmlinuz-2.6.16.60-0.54.5-smp root=/dev/sda1 vga=0x32b    resume=/dev/sda2 splash=silent showopts elevator=noop
by the way I think I added correctly

ok my question is
I can add this noop option on the fly by
Code:
echo "noop" > /sys/block/sda/queue/scheduler
but since I have sdb and sdc... I have to run that command three times it does not bother me I am worry about is what happens when my server is rebooted

there won't be any noop option for sdb and sdc since they are not included on my boot parameter

how can I automatically add noop to my sdb and sdc?

thanks a lot
 
Old 07-16-2010, 05:50 PM   #2
kopper27
Member
 
Registered: Nov 2009
Posts: 147

Original Poster
Rep: Reputation: 16
mmm I think I add

echo "noop" > /sys/block/sd[b/c]/queue/scheduler

to my /etc/rc.local
 
Old 07-16-2010, 06:26 PM   #3
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 14,832

Rep: Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820
With an elevator entry on the kernel line, you shouldn't need to update the sysfs entry(s).
 
Old 07-16-2010, 07:28 PM   #4
rayfordj
Member
 
Registered: Feb 2008
Location: Texas
Distribution: Fedora, RHEL, CentOS
Posts: 488

Rep: Reputation: 78
While I am not intimately familiar with SLES 10 & 11, specifically, setting the parameter at boot should set noop as the global default IO scheduler and further tuning should not be necessary. If it is not or you need different schedulers for distinct disks, however, rc.local is the way to change the scheduler used and/or any scheduler specific tuning parameters per-disk as there is currently no facility available like is with something like sysctl for /proc.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Fails to boot after IO scheduler noop registered Mithra Linux - Embedded & Single-board computer 2 10-31-2008 01:12 AM
the difference of kernel config option among different kernel version? rike_lin Linux - General 3 10-17-2008 08:17 PM
Noop Elevator Algorithm vduvvuru Linux - Kernel 2 03-10-2008 07:58 AM
snort - SHELLCODE x86 NOOP ddaas Linux - Security 7 06-17-2005 11:15 AM
kernel panic: try passing init= option to kernel...installation with Red Hat 9 kergen Linux - Hardware 1 09-30-2004 04:28 AM


All times are GMT -5. The time now is 08:45 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration