From: Kumaraparameshwaran Rathnavel <krath at cloudsimple.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Transport
Date: Tue, 25 Oct 2016 23:52:44 +0530 [thread overview]
Message-ID: <6D16B6E5-083D-4F22-83F2-67406B051BA3@cloudsimple.com> (raw)
In-Reply-To: 1477414585.2512.6.camel@intel.com
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
Hey thanks for the reply.
Can you please briefly explain me about the listener cm_id for incoming connections and active connection cm_id for incoming NVMe-OF requests.
Does this mean that initially when there is no connection established it is acceptor_poll and after the connection establishment it is connection cm_id.
Thanking You,
Param
> On 25-Oct-2016, at 10:26 PM, Walker, Benjamin <benjamin.walker(a)intel.com> wrote:
>
> On Tue, 2016-10-25 at 20:16 +0530, Kumaraparameshwaran Rathnavel wrote:
>> Hi Guys,
>>
>> Can you tell me the functionality difference between the aaceptor_poll and
>> conn_poll in the file rdma.c
>
> The acceptor_poll function should check the listener cm_id for incoming
> connections. The conn_poll should check the active connection cm_id for incoming
> NVMe-oF requests.
>
>>
>> Thanking you
>> Param
>>
>> Sent from my iPhone
>> _______________________________________________
>> SPDK mailing list
>> SPDK(a)lists.01.org
>> https://lists.01.org/mailman/listinfo/spdk
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2016-10-25 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 18:22 Kumaraparameshwaran Rathnavel [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-26 2:58 [SPDK] Transport Kumaraparameshwaran Rathnavel
2016-10-25 22:21 Walker, Benjamin
2016-10-25 16:56 Walker, Benjamin
2016-10-25 14:46 Kumaraparameshwaran Rathnavel
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=6D16B6E5-083D-4F22-83F2-67406B051BA3@cloudsimple.com \
--to=spdk@lists.01.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