From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Github issue #407 and libibverbs events
Date: Mon, 10 Sep 2018 16:46:34 +0000 [thread overview]
Message-ID: <19155b4fea7de44e231c7b168d972b1f66e2b9ca.camel@intel.com> (raw)
In-Reply-To: 122B872DCF83AB4DB816E25A2C1AD08D8BB6CF5C@IRSMSX102.ger.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On Mon, 2018-09-10 at 08:54 +0100, Szwed, Maciej wrote:
> Hi guys,
> I was investigating github issue #407 and found out that we don’t manage
> events in NVMf host side (perf in this case). We do that for NVMf target ->
> spdk_nvmf_process_cm/ib_event(). We should probably implement new poller that
> will handle incoming events in host side and change code accordingly. What do
> you think?
>
> Here is documentation for reference:
> https://pdfs.semanticscholar.org/9584/17ad2d476c0a4821925cf8474fabcb1229ce.pdf
> Chapter 3.7
>
Yes, we should be doing this. It is theoretically possible to transparently
recover from connection errors if we were to handle them on both the target and
the initiator side. Now that the target logic is in place, it's a great time to
go improve the initiator behavior.
> Regards,
> Maciek
next reply other threads:[~2018-09-10 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 16:46 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-10 7:54 [SPDK] Github issue #407 and libibverbs events Szwed, Maciej
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=19155b4fea7de44e231c7b168d972b1f66e2b9ca.camel@intel.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