From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: [RFC]: Removal of spinlocks/rw_locks in ccid3.c / packet_history.c:
Date: Sat, 03 Nov 2007 12:31:07 +0000 [thread overview]
Message-ID: <200711031350.20405@strip-the-willow> (raw)
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?
next reply other threads:[~2007-11-03 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 12:31 Gerrit Renker [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200711031350.20405@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=dccp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox