From: Tom Rainey <tom.rainey at samsung.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Posix framework on client
Date: Fri, 27 Sep 2019 21:44:14 +0000 [thread overview]
Message-ID: <80e63283da314000a65e58929abb2d85@samsung.com> (raw)
In-Reply-To: 1CCA1B4C-C4B4-4DED-A199-1814979D6C90@intel.com
[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]
Hi Jim,
Thanks for the pointer. That's what we needed.
-Tom
-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Harris, James R
Sent: Friday, September 27, 2019 2:04 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Posix framework on client
Hi Tom,
This is most likely a link issue with your client application Makefile. net_impls are activated via C constructor functions, so you need to use --whole_archive directives to ensure the linker doesn't optimize out the constructor function (since the constructor function isn't explicitly called anywhere).
See mk/spdk.app_vars.mk. SPDK uses constructor functions for registration in a lot of places, so by default we wrap all SPDK libraries with --whole_archive directives to ensure constructors don't get optimized out during link phase.
Hope that helps - please report back how it goes!
Regards,
-Jim
On 9/27/19, 1:56 PM, "SPDK on behalf of Tom Rainey" <spdk-bounces(a)lists.01.org on behalf of tom.rainey(a)samsung.com> wrote:
Hi,
We are attempting to use TCP to connect to a remote target, however, we noticed that our posix socket layer is not being loaded. When spdk_sock_connect is called, there does not seem to be any items in g_net_impls.
How does g_net_impls get populated on the client side? We've looked at the hello_sock sample and there doesn't seem to be anything tricky happening before spdk_sock_connect is called.
Thanks,
-Tom
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwIGaQ&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=TGM0bakVlcBrMpq-MEzqmroD2CrqAR3mlx-NLf9U4TU&m=1udY7g72tqf3g96ZtY29p0ErrT-e7MUYjloMBY5tzuM&s=YnnAuawXMkM9AxcBTumxiT-cRCz45B4XmVmtptDWZqg&e=
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwIGaQ&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=TGM0bakVlcBrMpq-MEzqmroD2CrqAR3mlx-NLf9U4TU&m=1udY7g72tqf3g96ZtY29p0ErrT-e7MUYjloMBY5tzuM&s=YnnAuawXMkM9AxcBTumxiT-cRCz45B4XmVmtptDWZqg&e=
next reply other threads:[~2019-09-27 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 21:44 Tom Rainey [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-27 21:04 [SPDK] Posix framework on client Harris, James R
2019-09-27 20:56 Tom Rainey
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=80e63283da314000a65e58929abb2d85@samsung.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