Hi!
I use old mars_nwe but have problems with its performance. It works really
poor. I would like to check if it's just IPX subsystem problem (== kernel
problem?) or just poor mars_nwe code. Unfortunately I can't find any IPX
benchmarks and I have no real Netware servers to compare. What can I do
Thank you for this elaborate clarification. I was indeed interested in #3,
although #1 and #2 are also interesting.
from what i recall, la_ctx measures #3. it does so by creating a ring
of unix processs connected with pipe, and then passes a token around,
each processes does some work polluting
Rafal Cygnarowski escreveu:
Hi!
I use old mars_nwe but have problems with its performance. It works really
poor. I would like to check if it's just IPX subsystem problem (== kernel
problem?) or just poor mars_nwe code. Unfortunately I can't find any IPX
benchmarks and I have no real Netware
Hi,
I noticed that the value of current macro has changed in the newer
kernel version (from 2.6.20?). It seems that now the task_struct
structure that points to the current process is now put in the FS
segment. That means from address range 0 upwards, we have the
current structure. Could anybody
Very good.
Now I'm trying to figure out why this tasklet_action() code path ends
up calling BUG(). This is a very intermittent problem and seemingly
impossible to reproduce.
404 if(!test_and_clear_bit(TASKLET_STATE_SCHED, t-state))
405 BUG();
It's obvious that 404 will result in
Hi,
Can any one kindly tell me what Software Interrupt exactly
means? Also, how is it different from the Hardware Interrupt?
Regards,
Aravind.
Dovie'andi se tovya sagain
-Mat Cauthon (WoT).
--
To unsubscribe from this list: send an email with
unsubscribe kernelnewbies to [EMAIL
Hi Aravind,
It pays to be precise when talking about these terms. Software
Interrupt is a bit of a misnomer because software never really
interrupts a cpu, it does not alter the sequence of instructions. Maybe
what you mean is; what is the difference between and interrupt and an
exception?
Hi.
I'm currently porting a framework developped by my research group for supporting
multiple interfaces/channels under linux 2.6.
I'm almost done, but I get some warnings when compiling:
WARNING: __divdf3 [/home/cf/netx-2.6/bonding/bonding.ko] undefined!
WARNING: __floatunsidf
I finally found the bug:
somewhere in the code there was a macro like (5.5 * 100)
the preprocessor expands this. as a floating point. And floating point is not
allowed in the kernel (well, it needs math-emu, which are the symbols that were
missing).
Man, it took me 1 day to figure that out...
TASKLET_STATE_SCHED is set when tasklet is scheduled using tasklet_schedule or
tasklet_hi_schedule and clear only when the tasklet starts its execution.
Are you using some customized kernel or stock kernel? I believe there should
not be this bug in stock kernel.
- Meraj
Tony Mouawad [EMAIL
10 matches
Mail list logo