All of lore.kernel.org
 help / color / mirror / Atom feed
* [RFC]: Removal of spinlocks/rw_locks in ccid3.c / packet_history.c:
@ 2007-11-03 12:31 Gerrit Renker
  2007-11-03 13:38 ` [RFC]: Removal of spinlocks/rw_locks in ccid3.c / Arnaldo Carvalho de Melo
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Gerrit Renker @ 2007-11-03 12:31 UTC (permalink / raw)
  To: dccp

With regard to the previous patch 9/9 I wonder if it is possible to remove the Reader/Writer spinlock used 
in the test tree in packet_history.c (field member @lock in struct tfrc_rx_hist). 

If the socket is protected by the socket lock, and the same backlog handler does not run concurrently, then
the RX history rw_lock is redundant. I haven't changed anything, but am about to reformat the patches so that
each of them compiles standalone, it is a good time to address this.

The point that I find confusing here is that several new cards (e.g. e1000) can have multiple TX/RX queues
on the same card: I wonder whether that will make a difference to the DCCP sk backlog handler.

Comments?

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-11-09 15:13 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-03 12:31 [RFC]: Removal of spinlocks/rw_locks in ccid3.c / packet_history.c: Gerrit Renker
2007-11-03 13:38 ` [RFC]: Removal of spinlocks/rw_locks in ccid3.c / Arnaldo Carvalho de Melo
2007-11-03 14:35 ` [RFC]: Removal of spinlocks/rw_locks in ccid3.c / packet_history.c: Gerrit Renker
2007-11-09 15:13 ` [RFC]: Removal of spinlocks/rw_locks in ccid3.c / packet_history.c Gerrit Renker

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.