All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: Robert Elliott <elliott@hpe.com>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH v2 1/4] pmemblk, dev-dax: load libpmem and libpmemblk at startup
Date: Wed, 11 Jan 2017 21:00:22 -0700	[thread overview]
Message-ID: <20170112040022.GC27546@kernel.dk> (raw)
In-Reply-To: <20170110212127.64926-1-elliott@hpe.com>

On Tue, Jan 10 2017, Robert Elliott wrote:
> From: Robert Elliott <elliott@hpe.com>
> 
> The pmemblk and dev-dax ioengines were loading libpmem.so and
> libpmemblk.so using dlopen() at runtime.
> 
> Although the upstream nvml Makefile installs a libpmem.so
> symbolic link, some of the distros (e.g. SUSE Linux Enterprise
> Server 12 SP2) are just installing so.1 symbolic links.  So,
> fio fails to find the libpmem.so and libpmemblk.so library files.
> 
> http://www.ibm.com/developerworks/linux/library/l-shlibs/index.html
> says applications should always load the versioned filenames to
> avoid compatibility issues; the non-versioned filenames are just
> for the compiler and linker.
> 
> Change ./configure to pass -lpmem and -lpmemblk to the compiler
> so the fio binary loads the versioned filename at startup like
> the other libraries, rather than open the non-versioned filename
> with dlopen() during runtime.
> 
> This way they show up in ldd:
> $ ldd fio
>         linux-vdso.so.1 (0x00007ffc290aa000)
>         libpmemblk.so.1 => /lib64/libpmemblk.so.1 (0x00007f65b5bc4000)
>         libpmem.so.1 => /lib64/libpmem.so.1 (0x00007f65b59be000)
>         libnuma.so.1 => /lib64/libnuma.so.1 (0x00007f65b57b3000)
>         librt.so.1 => /lib64/librt.so.1 (0x00007f65b55ab000)
>         libaio.so.1 => /lib64/libaio.so.1 (0x00007f65b53a9000)
>         libz.so.1 => /lib64/libz.so.1 (0x00007f65b5191000)
>         libm.so.6 => /lib64/libm.so.6 (0x00007f65b4e88000)
>         libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f65b4c6a000)
>         libdl.so.2 => /lib64/libdl.so.2 (0x00007f65b4a66000)
>         libc.so.6 => /lib64/libc.so.6 (0x00007f65b46a0000)
>         libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f65b449b000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000559f4d872000)

Added 1-4, thanks Robert.

-- 
Jens Axboe


      parent reply	other threads:[~2017-01-12  4:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  6:54 pmemblk and dev-dax cleanups Robert Elliott
2017-01-04  6:54 ` [PATCH 1/4] pmemblk, dev-dax: load libpmem and libpmemblk at startup Robert Elliott
2017-01-04 23:48   ` Elliott, Robert (Persistent Memory)
2017-01-04  6:54 ` [PATCH 2/4] pmemblk, dev-dax: Update descriptions Robert Elliott
2017-01-04  6:54 ` [PATCH 3/4] pmemblk,dev-dax: clean up error logs Robert Elliott
2017-01-04  6:54 ` [PATCH 4/4] pmemblk: Clarify fsize is in MiB not MB Robert Elliott
2017-01-05 18:47 ` pmemblk and dev-dax cleanups Jens Axboe
2017-01-10 21:21 ` [PATCH v2 1/4] pmemblk, dev-dax: load libpmem and libpmemblk at startup Robert Elliott
2017-01-10 21:21   ` [PATCH v2 2/4] pmemblk, dev-dax: Update descriptions Robert Elliott
2017-01-10 21:21   ` [PATCH v2 3/4] pmemblk, dev-dax: clean up error logs Robert Elliott
2017-01-10 21:21   ` [PATCH v2 4/4] pmemblk: Clarify fsize is in MiB not MB Robert Elliott
2017-01-12  4:00   ` Jens Axboe [this message]

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=20170112040022.GC27546@kernel.dk \
    --to=axboe@fb.com \
    --cc=elliott@hpe.com \
    --cc=fio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.