From: Kumaraparameshwaran Rathnavel <krath at cloudsimple.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Parse Subsystem
Date: Sun, 06 Nov 2016 23:25:08 +0530 [thread overview]
Message-ID: <1930099B-060D-400A-B10F-CE4C145A71FA@cloudsimple.com> (raw)
In-Reply-To: A98B2F79-DDA1-4480-AE85-BF8520EB40D8@cloudsimple.com
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
I understand that the event is enqueued in another core. The event is enqueued from the master core. So does that mean that until function returns from the master core the function in the another core will not be executed
Sent from my iPhone
> On 06-Nov-2016, at 10:25 PM, Kumaraparameshwaran Rathnavel <krath(a)cloudsimple.com> wrote:
>
> In the function spdk_nvmf_parse_subsystem the function nvmf_create_subsystem is called first which means that function calls spdk_get_io_channel is called for each space. But the namespaces are added only after this function call to the subsystem. How does this work?
>
> Thanking you,
> Param
next reply other threads:[~2016-11-06 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 17:55 Kumaraparameshwaran Rathnavel [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-06 16:55 [SPDK] Parse Subsystem 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=1930099B-060D-400A-B10F-CE4C145A71FA@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