bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: "libbpf/libbpf" 
	<reply+AAD4BK6TLXS3OGWEWHS5PTF4OTGSDEVBNHHCFBYSRA@reply.github.com>,
	bpf <bpf@vger.kernel.org>
Cc: "libbpf/libbpf" <libbpf@noreply.github.com>,
	Subscribed <subscribed@noreply.github.com>
Subject: Re: [libbpf/libbpf] Is it possible to do SHARED_UMEM between processes? (#138)
Date: Wed, 11 Mar 2020 08:15:33 -0700	[thread overview]
Message-ID: <CAEf4BzY7Qsu1aoN__nxyis4OgWvwWi5XJ9XJe3gOeEHJGdGFRw@mail.gmail.com> (raw)
In-Reply-To: <libbpf/libbpf/issues/138@github.com>

Adding bpf@vger.kernel.org, it's a better place to ask questions about
bpf and libbpf.

On Wed, Mar 11, 2020 at 6:48 AM Maximilian Gaul
<notifications@github.com> wrote:
>
> I am struggling with my project to get SHARED_UMEM running between two or more processes. I made some changes to the lib in order to be able to copy struct xsk_umem into shared memory.
>
> But now I get the error:
>
> symbol lookup error: /lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: _dl_allocate_tls, version GLIBC_PRIVATE
>
> In my opinion, a working example for SHARED_UMEM is strongly required. The only information I find about this topic is an e-mail from Nov, 2019 in the linux mailing list and two sentences from here : https://www.kernel.org/doc/html/latest/networking/af_xdp.html#xdp-shared-umem-bind-flag
>
> Please!!
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.

           reply	other threads:[~2020-03-11 15:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <libbpf/libbpf/issues/138@github.com>]

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=CAEf4BzY7Qsu1aoN__nxyis4OgWvwWi5XJ9XJe3gOeEHJGdGFRw@mail.gmail.com \
    --to=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=libbpf@noreply.github.com \
    --cc=reply+AAD4BK6TLXS3OGWEWHS5PTF4OTGSDEVBNHHCFBYSRA@reply.github.com \
    --cc=subscribed@noreply.github.com \
    /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;
as well as URLs for NNTP newsgroup(s).