online linux kernel documents

http://www.mjmwired.net/kernel/Documentation

network interface message level

just type

$sudo ethtool eth0

will gives you "Current message level"

how to change it?

sudo ethtool -s eth0 msglvl 0x00000001

irq stats

cat /proc/interrupts will show irq statistics w.r.t. cpus

 ChangeLog:   Started by Ingo Molnar    Update by Max Krasnyansky     SMP IRQ affinity    /proc/irq/IRQ#/smp_affinity and /proc/irq/IRQ#/smp_affinity_list specify  which target CPUs are permitted for a given IRQ source.  It's a bitmask  (smp_affinity) or cpu list (smp_affinity_list) of allowed CPUs.  It's not  allowed to turn off all CPUs, and if an IRQ controller does not support  IRQ affinity then the value will not change from the default of all cpus.    /proc/irq/default_smp_affinity specifies default affinity mask that applies  to all non-active IRQs. Once IRQ is allocated/activated its affinity bitmask  will be set to the default mask. It can then be changed as described above.  Default mask is 0xffffffff.    Here is an example of restricting IRQ44 (eth1) to CPU0-3 then restricting  it to CPU4-7 (this is an 8-CPU SMP box):    [root@moon 44]# cd /proc/irq/44  [root@moon 44]# cat smp_affinity  ffffffff    [root@moon 44]# echo 0f > smp_affinity  [root@moon 44]# cat smp_affinity  0000000f  [root@moon 44]# ping -f h  PING hell (195.4.7.3): 56 data bytes  ...  --- hell ping statistics ---  6029 packets transmitted, 6027 packets received, 0% packet loss  round-trip min/avg/max = 0.1/0.1/0.4 ms  [root@moon 44]# cat /proc/interrupts | grep 'CPU\|44:'             CPU0       CPU1       CPU2       CPU3      CPU4       CPU5        CPU6       CPU7   44:       1068       1785       1785       1783         0          0           0         0    IO-APIC-level  eth1    As can be seen from the line above IRQ44 was delivered only to the first four  processors (0-3).  Now lets restrict that IRQ to CPU(4-7).    [root@moon 44]# echo f0 > smp_affinity  [root@moon 44]# cat smp_affinity  000000f0  [root@moon 44]# ping -f h  PING hell (195.4.7.3): 56 data bytes  ..  --- hell ping statistics ---  2779 packets transmitted, 2777 packets received, 0% packet loss  round-trip min/avg/max = 0.1/0.5/585.4 ms  [root@moon 44]# cat /proc/interrupts |  'CPU\|44:'             CPU0       CPU1       CPU2       CPU3      CPU4       CPU5        CPU6       CPU7   44:       1068       1785       1785       1783      1784       1069        1070       1069   IO-APIC-level  eth1    This time around IRQ44 was delivered only to the last four processors.  i.e counters for the CPU0-3 did not change.    Here is an example of limiting that same irq (44) to cpus 1024 to 1031:    [root@moon 44]# echo 1024-1031 > smp_affinity  [root@moon 44]# cat smp_affinity  1024-1031    Note that to do this with a bitmask would require 32 bitmasks of zero  to follow the pertinent one.

Launching xclock at remote using ssh

first, at remote enable accessing x from remote node by

remote$ xhost + remote-node

Then, at local, access remote using ssh (be sure X-forwarding is disabled)

then,

remote$ DISPLAY=:0 xclock

Deleting matching lines

in vim

:g/pattern/d

in sed

sed '/pattern/d' file

[Eclipse] If you encounter this error message

Cannot complete the install because one or more required items could not be found. Software being installed: Android Development Tools 15.0.0.v201110251216-213216 (com.android.ide.eclipse.adt.feature.group 15.0.0.v201110251216-213216) Missing requirement: Android Development Tools 15.0.0.v201110251216-213216 (com.android.ide.eclipse.adt.feature.group 15.0.0.v201110251216-213216) requires 'org.eclipse.wst.sse.core 0.0.0' but it could not be found

While installing android adt plugin, you probably missing a library with ssl.
So just try this.

$ sudo apt-get install openssl libssl-dev

[Eclipse] eclipse launching fails

Eclipse fails with the following logs.

!SESSION 2011-11-07 23:51:29.573 -----------------------------------------------
eclipse.buildId=M20100211-1343
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86

!ENTRY org.eclipse.osgi 4 0 2011-11-07 23:51:29.699
!MESSAGE Startup error
!STACK 1
java.lang.IllegalArgumentException: invalid qualifier: 44+drm33
at org.osgi.framework.Version.validate(Version.java:188)
at org.osgi.framework.Version.(Version.java:92)
at org.eclipse.osgi.framework.internal.core.Framework.initializeProperties(Framework.java:361)
at org.eclipse.osgi.framework.internal.core.Framework.initialize(Framework.java:196)
at org.eclipse.osgi.framework.internal.core.Framework.(Framework.java:157)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:286)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)

It seems eclipse does not take the kernel name with '44+drm33' as argument.
FYI, uname -r gives '2.6.32.44+drm33.19'

Fortunately there is a thread about this bug in Ubuntu

https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/600584