lkml.org 
[lkml]   [2006]   [Jun]   [8]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateThu, 08 Jun 2006 08:30:37 +0200
FromStefan Richter <>
SubjectRe: 2.6.17-rc6-mm1
Chris Wright wrote:
> * Stefan Richter (stefanr@s5r6.in-berlin.de) wrote:
>>The pending_packet_queue is only accessed from within 
>>drivers/ieee1394/ieee1394_core.c, and only via net/core/skbuff.c's 
>>access functions for queueing/ dequeueing/ queuewalking. Or am I missing 
>>something?
> 
> Quick grep show following two irq handlers as examples:
> 
> ohci_irq_handler() | lynx_irq_handler()
>   hpsb_bus_reset()
>     abort_requests()
>       skb_dequeue()
>         spin_lock_irqsave()
> 
> That spin_lock is called directly from within irq handler.

Yes, definitely. What I wanted to reassure myself about was rather that 
no other net/ code besides skbuff.c's touches this queue. IOW only the 
ieee1394 low and mid layer control the contexts within which the queue 
lock is used.
-- 
Stefan Richter
-=====-=-==- -==- -=---
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
\
 
 \ /
  Last update: 2006-06-08 08:36    [from the cache]
©2003-2008