From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [v3 PATCH 0/2] Add RCU locking to SCTPaddress management
Date: Mon, 17 Sep 2007 09:44:45 -0400 [thread overview]
Message-ID: <46EE84CD.2070104@hp.com> (raw)
In-Reply-To: <20070916.160102.54198849.davem@davemloft.net>
David Miller wrote:
> From: Vlad Yasevich <vladislav.yasevich@hp.com>
> Date: Thu, 13 Sep 2007 15:34:35 -0400
>
>> Thanks to Sridhar Samudral and Paul McKenney for all the help and comments.
>> I think this is a final version, unless someone else can spot more problems.
>> I've ran this under heavy load and it the patches behaves well.
>>
>> I think patch 1 is a candidate for 2.6.23 since it fixes a bug, but splitting
>> these seems a bit odd to me. I'll leave it to DaveM to decide where to
>> put them.
>
> Since you tested this well, I've decided to put both of these
> patches into net-2.6
>
> I agree it's stupid to split them up.
>
> There'll be some merge hassles when I rebase net-2.6.24, but
> that tree is such a monster that this is inevitable for every
> bug fix I queue up for 2.6.23 :-)
>
Thanks Dave. If you want me to take a look at these issues, let me know.
-vlad
prev parent reply other threads:[~2007-09-17 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 19:34 [v3 PATCH 0/2] Add RCU locking to SCTPaddress management Vlad Yasevich
2007-09-13 19:34 ` [v3 PATCH 1/2] SCTP: Add RCU synchronization around sctp_localaddr_list Vlad Yasevich
2007-09-13 19:57 ` Sridhar Samudrala
2007-09-13 19:34 ` [v3 PATCH 2/2] SCTP: Convert bind_addr_list locking to RCU Vlad Yasevich
2007-09-13 20:00 ` Sridhar Samudrala
2007-09-16 23:01 ` [v3 PATCH 0/2] Add RCU locking to SCTPaddress management David Miller
2007-09-17 13:44 ` Vlad Yasevich [this message]
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=46EE84CD.2070104@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).