From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: Netdev List <netdev@vger.kernel.org>,
lksctp-developers@lists.sourceforge.net
Subject: Re: SCTP control socket question
Date: Thu, 27 Mar 2008 08:48:20 -0400 [thread overview]
Message-ID: <47EB9794.7010407@hp.com> (raw)
In-Reply-To: <1206619433.32459.9.camel@iris.sw.ru>
Denis V. Lunev wrote:
> Hello, Vlad!
>
> I have read SCTP sources and found that SCTP control socket
> (sctp_ctl_socket) remains hashed unlike similar staff in UDP/TCP etc.
>
> Am I wrong, that it should not be hashed or not?
Why do you believe that the socket is hashed? That socket is only
allocated and referenced. It's should not be in any hash tables
since we hold a global reference on it.
-vlad
next prev parent reply other threads:[~2008-03-27 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 12:03 SCTP control socket question Denis V. Lunev
2008-03-27 12:48 ` Vlad Yasevich [this message]
2008-03-27 13:09 ` Denis V. Lunev
2008-03-27 13:15 ` Vlad Yasevich
2008-03-27 13:43 ` Denis V. Lunev
2008-03-27 14:01 ` Vlad Yasevich
2008-03-27 14:15 ` Pavel Emelyanov
2008-03-28 3:30 ` 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=47EB9794.7010407@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=den@openvz.org \
--cc=lksctp-developers@lists.sourceforge.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).