All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: dccp@vger.kernel.org
Subject: Re: [RFC]: Removal of spinlocks/rw_locks in ccid3.c /
Date: Sat, 03 Nov 2007 13:38:18 +0000	[thread overview]
Message-ID: <20071103133817.GA3780@ghostprotocols.net> (raw)
In-Reply-To: <200711031350.20405@strip-the-willow>

Em Sat, Nov 03, 2007 at 01:50:20PM +0000, Gerrit Renker escreveu:
> 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?

I think that you are right, we can't process two packets at the same
time for the same socket, more locks than the socket lock are not needed
at all.

With regards to multiple tx/rx queues: same reasoning applies, multiple
packets are being received/sent, but per socket serialization happens at
l4.

- Arnaldo

  reply	other threads:[~2007-11-03 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03 12:31 [RFC]: Removal of spinlocks/rw_locks in ccid3.c / packet_history.c: Gerrit Renker
2007-11-03 13:38 ` Arnaldo Carvalho de Melo [this message]
2007-11-03 14:35 ` 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=20071103133817.GA3780@ghostprotocols.net \
    --to=acme@redhat.com \
    --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 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.