Newsgroup: it.comp.os.linux.iniziare
Titolo: ubuntu e kernel

si puo compilare il kernel da versione 386 a 686 ?
esiste un tool grafico per fare cio ?
e' un p4 ht e farlo andare con kernel 386 mi pare sprecato
--
comunque ad un primo impatto (sono nuovo di linux) ho notato:
hardware riconoscito (wifi, rete, video, modem intel(non testato), audio)
php apache mysql (andanti basta selezionare i pacchetti)
aggiunto da poco mysql administrator
voto 8
Questa e' la giusta strada per linux andare senza romprere troppo le scatole

 e' un p4 ht e farlo andare con kernel 386 mi pare sprecato
Installa linux-image-686

 Installa linux-image-686
per selezionarlo all'avvio (esc)
cmq sai che e' piu veloce a partire :-)
disco ntfs usb montato (ho installato automount) per metterlo in write ?

 
Sprecato?
Gli sviluppatori di Ubuntu stanno giusto valutando se eliminare dalla 
distro i vari kernel ottimizzati poiche' dai test che hanno eseguito 
sembra che le prestazioni maggiori derivino piu' dalla suggestione degli 
utenti che da un reale aumento di performance umanamente riscontrabile. 
Puoi dare uno sguardo alla discussione tuttora in corso nella mailing 
list degli sviluppatori...dove ci sono anche un bel po' di test 
effettuati...
----------------------------------------------------------------------
Test was performed on an Intel Pentium 4, 2Ghz system with 256Mb of RAM.
I consider this about average for our users. The test I ran was
"contest", which basically builds a kernel under several different load
types. It's meant specifically for comparing different kernels on the
same machine. Each one of the lines below represents the average of 3
kernel builds under that particular type of stress. The first two are
baseline results (cache run is just no_load without clearing the
mem/disk cache, the rest of the results have the mem/disk cache cleared
before starting).
Here's the results:
no_load:
Kernel       [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-6-386      3	73	87.7	0.0	0.0	1.00
2.6.17-6-686      3	73	89.0	0.0	0.0	1.00
cacherun:
Kernel       [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-6-386      3	65	98.5	0.0	0.0	0.89
2.6.17-6-686      3	66	97.0	0.0	0.0	0.90
process_load:
Kernel       [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-6-386      3	143	44.8	260.0	52.4	1.96
2.6.17-6-686      3	144	44.4	230.0	52.8	1.97
ctar_load:
Kernel       [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-6-386      3	100	67.0	8.7	10.0	1.37
2.6.17-6-686      3	97	69.1	6.3	9.3	1.33
xtar_load:
Kernel       [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-6-386      3	96	67.7	2.0	4.2	1.32
2.6.17-6-686      3	96	68.8	1.7	4.1	1.32
io_load:
Kernel       [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-6-386      3	102	64.7	11.3	5.9	1.40
2.6.17-6-686      3	103	66.0	12.1	8.3	1.41
io_other:
Kernel       [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-6-386      3	94	71.3	20.9	12.8	1.29
2.6.17-6-686      3	97	70.1	21.3	16.3	1.33
read_load:
Kernel       [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-6-386      3	91	72.5	2.3	2.2	1.25
2.6.17-6-686      3	92	72.8	2.3	2.2	1.26
list_load:
Kernel       [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-6-386      3	87	75.9	0.0	5.7	1.19
2.6.17-6-686      3	87	77.0	0.0	6.9	1.19
mem_load:
Kernel       [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-6-386      3	327	20.5	74.0	0.6	4.48
2.6.17-6-686      3	390	17.7	80.7	0.8	5.34
dbench_load:
Kernel       [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-6-386      3	83	78.3	52193.3	18.1	1.14
2.6.17-6-686      3	92	71.7	47986.7	23.9	1.26
Using this as a guide, you can see that the difference is only
negligible. The -686 targeted kernel does not gain or lose any
significant performance on this test system. The mem_load was the only
noticeable change, where the -686 kernel shows worse performance. This
may be specific to my system. The individual results are here:
2.6.17-6-386 58 9 157 764901 883 mem_load 0 2 158 182219 5893 7100
2.6.17-6-386 58 10 381 780220 4597 mem_load 0 3 382 191532 8976 7600
2.6.17-6-386 59 10 445 780181 6654 mem_load 0 2 446 191709 8501 7500
2.6.17-6-686 58 11 244 771704 1849 mem_load 0 3 244 192658 7983 7600
2.6.17-6-686 58 12 445 788730 6357 mem_load 1 3 446 198200 9831 8100
2.6.17-6-686 59 12 481 793676 6401 mem_load 1 3 482 200208 11464 8500
You can see in the 4th column the major changes in the results of the
first run for each kernel. The results after the first run seem more
likely to be correct.
I also performed the same test on an SMP Xeon machine (2 x Core2Duo @
3ghz), using the amd64-generic and amd64-xeon kernel images. Here's the
results for that:
no_load:
Kernel                 [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-7-amd64-generic      3	49	357.1	0.0	0.0	1.00
2.6.17-7-amd64-xeon         3	47	370.2	0.0	0.0	1.00
cacherun:
Kernel                 [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-7-amd64-generic      3	48	362.5	0.0	0.0	0.98
2.6.17-7-amd64-xeon         3	47	368.1	0.0	0.0	1.00
process_load:
Kernel                 [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-7-amd64-generic      3	60	285.0	131.0	95.1	1.22
2.6.17-7-amd64-xeon         3	60	285.0	130.0	96.7	1.28
ctar_load:
Kernel                 [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-7-amd64-generic      3	55	320.0	15.7	25.5	1.12
2.6.17-7-amd64-xeon         3	54	325.9	15.3	25.9	1.15
xtar_load:
Kernel                 [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-7-amd64-generic      3	51	343.1	1.7	5.9	1.04
2.6.17-7-amd64-xeon         3	53	330.2	2.3	7.5	1.13
io_load:
Kernel                 [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-7-amd64-generic      3	101	171.3	3.8	5.9	2.06
2.6.17-7-amd64-xeon         3	97	179.4	3.7	5.6	2.06
io_other:
Kernel                 [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-7-amd64-generic      3	115	150.4	3.8	5.9	2.35
2.6.17-7-amd64-xeon         3	103	168.0	3.7	5.5	2.19
read_load:
Kernel                 [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-7-amd64-generic      3	89	194.4	0.4	0.0	1.82
2.6.17-7-amd64-xeon         3	93	186.0	0.4	0.0	1.98
list_load:
Kernel                 [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-7-amd64-generic      3	49	357.1	0.0	2.0	1.00
2.6.17-7-amd64-xeon         3	53	328.3	0.0	0.0	1.13
mem_load:
Kernel                 [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-7-amd64-generic      3	54	338.9	3137.0	38.9	1.10
2.6.17-7-amd64-xeon         3	54	337.0	3155.3	38.9	1.15
dbench_load:
Kernel                 [runs]	Time	CPU%	Loads	LCPU%	Ratio
2.6.17-7-amd64-generic      3	84	211.9	0.0	0.0	1.71
2.6.17-7-amd64-xeon         3	86	207.0	0.0	0.0	1.83
The only significant different was in the io_other performance. The
io_other test involves some random I/O operations on a large file. I
think the difference here is real. However, given that our -server
kernel will likely get back the small loss should be enough to warrant
still converting to generic kernels for amd64 and i386.
I can make this happen using linux-meta to handle the upgrades (next
kernel upload is an ABI bump, so would be perfect timing along with lrm
and linux-meta).
----------------------------------------------------------------------
Ciiips
Aragorn