Gentoo Archives: gentoo-amd64

From: Fernando Boaglio <boaglio@×××××.com>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] [gentoo-amd64 Gentoo Linux Tuning Guide
Date: Sat, 29 Apr 2006 04:11:45
Message-Id: ab2953b00604282110g329760f5kb3e16cb8b2ceaaea@mail.gmail.com
In Reply to: Re: [gentoo-amd64] [gentoo-amd64 Gentoo Linux Tuning Guide by Chris Wall
1 Guys,
2
3 After a kernel rebuild my machine was pretty fast! =D
4
5 My new config:
6
7 cat /usr/src/linux/.config | grep -i cpu
8 # CONFIG_GENERIC_CPU is not set
9 CONFIG_X86_CPUID=y
10 CONFIG_SPLIT_PTLOCK_CPUS=4
11 # CPU Frequency scaling
12 CONFIG_CPU_FREQ=y
13 CONFIG_CPU_FREQ_TABLE=y
14 # CONFIG_CPU_FREQ_DEBUG is not set
15 CONFIG_CPU_FREQ_STAT=y
16 # CONFIG_CPU_FREQ_STAT_DETAILS is not set
17 CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
18 # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
19 CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
20 # CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
21 # CONFIG_CPU_FREQ_GOV_USERSPACE is not set
22 # CONFIG_CPU_FREQ_GOV_ONDEMAND is not set
23 # CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
24 # CPUFreq processor drivers
25 # CONFIG_X86_ACPI_CPUFREQ is not set
26 # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
27
28 Since I'm running a desktop machine, not a laptop, I removed all non
29 related options.
30
31 Chris, no problem with my DMA:
32
33 >hdparm /dev/hda
34 /dev/hda:
35 multcount = 16 (on)
36 IO_support = 1 (32-bit)
37 unmaskirq = 1 (on)
38 using_dma = 1 (on)
39 keepsettings = 0 (off)
40 readonly = 0 (off)
41 readahead = 256 (on)
42 geometry = 65535/16/63, sectors = 156250000, start = 0
43
44 Thanks for all tips everybody!
45
46
47 On 4/27/06, Chris Wall <chris.wall@××××××××.com> wrote:
48 > Fernando Boaglio wrote:
49 >
50 > >Hmm...
51 > >
52 > >Please check my kernel config file:
53 > >
54 > >
55 > >
56 > >>cat /usr/src/linux/.config | grep -i cpu
57 > >>
58 > >>
59 > ># CONFIG_GENERIC_CPU is not set
60 > >CONFIG_X86_CPUID=y
61 > >CONFIG_SPLIT_PTLOCK_CPUS=4
62 > ># CPU Frequency scaling
63 > >CONFIG_CPU_FREQ=y
64 > >CONFIG_CPU_FREQ_TABLE=y
65 > ># CONFIG_CPU_FREQ_DEBUG is not set
66 > >CONFIG_CPU_FREQ_STAT=y
67 > ># CONFIG_CPU_FREQ_STAT_DETAILS is not set
68 > >CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
69 > ># CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
70 > >CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
71 > >CONFIG_CPU_FREQ_GOV_POWERSAVE=y
72 > >CONFIG_CPU_FREQ_GOV_USERSPACE=y
73 > >CONFIG_CPU_FREQ_GOV_ONDEMAND=y
74 > >CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
75 > ># CPUFreq processor drivers
76 > ># CONFIG_X86_ACPI_CPUFREQ is not set
77 > ># CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
78 > >
79 > >Should I change anything ?
80 > >
81 > >Maybe I should remove CONFIG_CPU_FREQ_GOV_CONSERVATIVE and
82 > >CONFIG_CPU_FREQ_GOV_POWERSAVE...
83 > >
84 > >=)
85 > >
86 > >On 4/27/06, Sergio Polini <sp_rm_it@×××××.it> wrote:
87 > >
88 > >
89 > >>Fernando Boaglio:
90 > >>
91 > >>
92 > >>>It's not about startup time, it's about running time, sometimes the
93 > >>>systems freezes
94 > >>>a little bit, just like asking for more CPU or RAM.
95 > >>>
96 > >>>
97 > >>I'ld look at the cpu frequency governor.
98 > >>From /usr/src/linux/drivers/cpufreq/Kconfig, about the 'conservative'
99 > >>governor:
100 > >>
101 > >>"If you have a desktop machine then you should really be considering
102 > >>the 'ondemand' governor instead, however if you are using a laptop,
103 > >>PDA or even an AMD64 based computer (due to the unacceptable
104 > >>step-by-step latency issues between the minimum and maximum frequency
105 > >>transitions in the CPU) you will probably want to use this governor."
106 > >>
107 > >>As far as I can understand, this means that AMD64 takes "a lot" of
108 > >>time to switch between two frequencies, so "the system freezes a
109 > >>little bit" when this happens.
110 > >>
111 > >>This is why I've choosen the conservative governor for my HP dv5000
112 > >>laptop.
113 > >>
114 > >>My 2 cents ;-)
115 > >>
116 > >>Sergio
117 > >>
118 > >>--
119 > >>gentoo-amd64@g.o mailing list
120 > >>
121 > >>
122 > >>
123 > >>
124 > >
125 > >
126 > >--
127 > >[]'s
128 > >boaglio@×××××.com
129 > >
130 > >
131 > >
132 > Also, check your hard drive parameters and make sure DMA is on. I
133 > always get tripped up by this between an Intel 2.53 machine and my AMD64
134 > 3200+ machine. It seems that everytime I rebuild the kernel on the
135 > AMD64 I forget to set the correct values for DMA access.
136 > Chris
137 > --
138 > gentoo-amd64@g.o mailing list
139 >
140 >
141
142
143
144 --
145 []'s
146 boaglio@×××××.com
147
148 --
149 gentoo-amd64@g.o mailing list