* profile code added to netif_receive_skb function
@ 2007-11-26 5:46 kernel coder
2007-11-27 4:00 ` Valdis.Kletnieks
0 siblings, 1 reply; 2+ messages in thread
From: kernel coder @ 2007-11-26 5:46 UTC (permalink / raw)
To: linux-kernel
hi,
I have added some code to netif_receive_skb function.As linux kernel
is multhreaded , so there is no gaurantee than mine code is completely
executed without being disturbed by any other process .Timer interrupt
handler is an example of code which might interrupt execution of mine
code.
I just want to observe which processes are disturbing mine code .I
think i need to print EIP register values .How can i print cache
contents as well in linux kernel .Are there any tools available for
such purpose
thanks,
shahzad
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: profile code added to netif_receive_skb function
2007-11-26 5:46 profile code added to netif_receive_skb function kernel coder
@ 2007-11-27 4:00 ` Valdis.Kletnieks
0 siblings, 0 replies; 2+ messages in thread
From: Valdis.Kletnieks @ 2007-11-27 4:00 UTC (permalink / raw)
To: kernel coder; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
On Sun, 25 Nov 2007 21:46:26 PST, kernel coder said:
> hi,
>
> I have added some code to netif_receive_skb function.As linux kernel
> is multhreaded , so there is no gaurantee than mine code is completely
> executed without being disturbed by any other process .Timer interrupt
> handler is an example of code which might interrupt execution of mine
> code.
The trick is to write your code so it doesn't *matter* if other code runs.
For example - the timer interrupt almost certainly doesn't look at or modify
any of *your* code's variables. So 98% of the kernel's code you don't
even have to *care* if it runs (as long as you aren't doing something
real-time or has similar response-time or throughput constraints).
And if you are worried about that other 2%, where related code, for example the
IRQ handler for a network interface, may have to look at and/or modify some of
your variables, that's when you should be using appropriate locking - there's
mutexes, semaphores, the whole RCU family, and more - none of which I'll
attempt to explain, because I'm not all that good at that stuff.
Basic rule of thumb - if you have something that will break if two things
access it at the same time, put a lock around it, so they take turns.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-11-27 4:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-11-26 5:46 profile code added to netif_receive_skb function kernel coder
2007-11-27 4:00 ` Valdis.Kletnieks
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®