From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EE5AEC10F27 for ; Wed, 11 Mar 2020 15:15:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4464D206E9 for ; Wed, 11 Mar 2020 15:15:45 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="YzGAA2/Y" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729511AbgCKPPp (ORCPT ); Wed, 11 Mar 2020 11:15:45 -0400 Received: from mail-qk1-f194.google.com ([209.85.222.194]:39927 "EHLO mail-qk1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729408AbgCKPPp (ORCPT ); Wed, 11 Mar 2020 11:15:45 -0400 Received: by mail-qk1-f194.google.com with SMTP id e16so2402644qkl.6 for ; Wed, 11 Mar 2020 08:15:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=8+41engWsi9UoZh82ULHGWmLZ87Gc36Sb5PUQS0Hglg=; b=YzGAA2/Yx4cGcjMX6es7Pchi0Ndd7QQ01SCV6Y8F7Y0L75D17Gc2DrNb39FRqVUh9Z HGT/97GGFKmC6Z0Y+WN6boGgBjMTRPo1fkV17l2ApMaYI3otBzQIQTL07/Q1Sp5G7+F2 hlxA2cO3V2rhzqOFYOrpOU5TUyMUDeMF7oQhvj9ULsnXuAk7+08aaB9/4dCG2Pj2Gs8s 6Ry8CiW8TX5PLBBDPEAiZVhDoXFkVWz+gIW22UPAGx6nnRdXPeaoZQizg2f/PJRJ6pNY DKPCkIKoBQXm3vwPz32tLxpjdOVs/NlNu87NOvQGq4MyeFdTvjI8CEIkZhwLquOA1FG3 A7Eg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=8+41engWsi9UoZh82ULHGWmLZ87Gc36Sb5PUQS0Hglg=; b=tPVUBbstqplk5lpFH9oYDrtBbuBUeV/BdOgX4nuXLT6C9owsJgC0vI+aReD4f/DIqx 7LtFjV1klpWPn+bJ9bOq9Z1dMBxA/VSTztzNnLhnDpmK3n4Na6jAD5i9UK3M0h2kV4h1 o75UPv0UtmvNl5N+cwNtq/rnTW7NirkTDrATLJkQbdqhzJjVhNxwvWVB1MK0mWsadbI4 Hy+TsrgEgY5RjSXVHGtEikYsfAnifa0YIounzJJEW3MdClsW0eow1RIr6D1cAkpVDhOh Y+6HbW7dF0lltrCKSxfugK9aoMBHXf8sRaNQlnFpjos2mhWaBHzUs2LnQNNvRoXC3xqe fWbA== X-Gm-Message-State: ANhLgQ1BH6mtyHyr2hFFrqRZwxwPb2zmKVRam55vKBYe1vyUEfZ0/Euk PoUT0W6pbTZYxUGmJdgi7vvvyXUHLK4EJuRSJWw= X-Google-Smtp-Source: ADFU+vu72uwN90JjWBzsYhGPYUvE3v/4V4FH8VJ+qPA6hKVsCFjFnSlAWm1V54W7nIATHYbwAZ0ADNh09FhFnzQyGS4= X-Received: by 2002:a37:e40d:: with SMTP id y13mr3268469qkf.39.1583939744144; Wed, 11 Mar 2020 08:15:44 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Andrii Nakryiko Date: Wed, 11 Mar 2020 08:15:33 -0700 Message-ID: Subject: Re: [libbpf/libbpf] Is it possible to do SHARED_UMEM between processes? (#138) To: "libbpf/libbpf" , bpf Cc: "libbpf/libbpf" , Subscribed Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: bpf-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org 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 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 sym= bol: _dl_allocate_tls, version GLIBC_PRIVATE > > In my opinion, a working example for SHARED_UMEM is strongly required. Th= e only information I find about this topic is an e-mail from Nov, 2019 in t= he 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!! > > =E2=80=94 > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or unsubscribe.