From: Marcelo Leitner <mleitner@redhat.com>
To: Flavio Leitner <fbl@redhat.com>
Cc: netdev <netdev@vger.kernel.org>, Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH 2/2] tcp: bind() optimize port allocation
Date: Wed, 25 Jan 2012 16:36:49 -0200 [thread overview]
Message-ID: <4F204BC1.9070407@redhat.com> (raw)
In-Reply-To: <1327516492-9045-2-git-send-email-fbl@redhat.com>
On 01/25/2012 04:34 PM, Flavio Leitner wrote:
> Port autoselection finds a port and then drop the lock,
> then right after that, gets the hash bucket again and lock it.
>
> Fix it to go direct.
>
> Signed-off-by: Flavio Leitner<fbl@redhat.com>
Signed-off-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
next prev parent reply other threads:[~2012-01-25 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 18:34 [PATCH 1/2] tcp: bind() fix autoselection to share ports Flavio Leitner
2012-01-25 18:34 ` [PATCH 2/2] tcp: bind() optimize port allocation Flavio Leitner
2012-01-25 18:36 ` Marcelo Leitner [this message]
2012-01-25 18:48 ` Eric Dumazet
2012-01-26 2:51 ` David Miller
2012-01-25 18:36 ` [PATCH 1/2] tcp: bind() fix autoselection to share ports Marcelo Leitner
2012-01-25 18:47 ` Eric Dumazet
2012-01-26 2:50 ` David Miller
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=4F204BC1.9070407@redhat.com \
--to=mleitner@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=fbl@redhat.com \
--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).