From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 41C1842947 for ; Sat, 15 Apr 2023 04:46:39 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C355240A8A; Sat, 15 Apr 2023 04:46:38 +0200 (CEST) Received: from mail-pl1-f176.google.com (mail-pl1-f176.google.com [209.85.214.176]) by mails.dpdk.org (Postfix) with ESMTP id CD31740697 for ; Sat, 15 Apr 2023 04:46:36 +0200 (CEST) Received: by mail-pl1-f176.google.com with SMTP id lh8so7283295plb.1 for ; Fri, 14 Apr 2023 19:46:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681526796; x=1684118796; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=okXQYjr9izexg7ZS6XnKNnpCNGhdEWB/DKsU/kagNg0=; b=NyUp9Fgd1WBsBHPGJzBhyy9sbaRObh93jP2YLBnJ7+ZdwRcHI58KlRIi47VJVEIL0d Abul4FyEGWowIQhVeQJaSd4zZaGRLS+APkRfxJrUVKOKOQc7Jak1NK8b7+oZ4vALrAnw a4njJb699IMv5VMuanRW5uGNlGKWjwjF677d3XV+9tHL2xuDEjuIe8MCIdo0nPYBL0ec pkUG0dCg2FQGnbfZwoPKGox7KzqvsjPjGjIFyHmU229vETgnlW9Fxow2FJiQRNZqZ2GP EwprFGkTdT91JGASrtQGrMbusYypiyIwlWAR6ItEGGg0+a5bK7rIU/MMOcSdk7KxVC7j 2v/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681526796; x=1684118796; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=okXQYjr9izexg7ZS6XnKNnpCNGhdEWB/DKsU/kagNg0=; b=R2RxeIVo39Kd5zcfRN/v/GhEpN7B5GFMoxVsRK3/SBg28ntou+tc8YyvqlFPAoA7H8 Kt/4x644OAhXMsETV6zssi/Lvcyn7lCdGa1gNCKNeIrAPG3i1j3r1m0eHceaUeMf45u0 U5COgZA8evK0gh2DCK4q8bwHVkeBWHHryKqinDhu6Vlw9An7GR1vy6NGZz66Y6OiENHW fvrjuHTVKYxkvyhqeLcntkPQ2yXPHGbEKa9VZXuRR2Kbx/NfgCbi8uTgqJz8cD94zz7+ rAgpLpYQ/JVQwD2BpacvrJRBHGKQXWW02RsZtY+XxNpbMt3PsAqClkPhKkSNUedA6BwO dKxA== X-Gm-Message-State: AAQBX9cuv49xvZ10Jd+zPYllYY5LPd+h8I6g5xDao5FIXncF4hO68Lhv 5cg9hTsHLYv1ov0fZM6zSx67NJndMT0cxRRTsUROIgKuNU/Yojg/ X-Google-Smtp-Source: AKy350a9w98RN9jx/fVgDIdGyT0ebh4SSFdzIAJm4wiv7IWwh0VBbUPYDHOEn99UVBK4Dpm6h1BTjesKrE0DZ1/XHPw= X-Received: by 2002:a17:902:e84a:b0:1a6:9a20:f252 with SMTP id t10-20020a170902e84a00b001a69a20f252mr1642329plg.7.1681526795854; Fri, 14 Apr 2023 19:46:35 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "J.J. Martzki" Date: Sat, 15 Apr 2023 10:46:52 +0800 Message-ID: Subject: Re: Use case understanding for l3fwd To: Dinesh Kumar Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org > Is this process correct to assign IP and then device to DPDK? No, after binding the driver to vfio/uio, the IP configuration is no longer available. The IP is something belonging to an application, not a driver (DPDK). > Is there any way to see ip and ethernet address after binding to DPDK? MAC is available for the rte_eth_dev, there's some API like rte_eth_macaddr_get() to get MAC from a specific port. l3fwd should have some CLI commands for getting MAC ethier, maybe you can read it's documents. IP is not available as I said before. BTW, your topo is confusing. Are you running 2 l3fwd in 2 separate VMs? It's not gonna work. AFAK, l3fwd switches packets from ports which attached to it. You can't use 2 separate l3fwd to connect 2 VMs. If you are tring to connect 2 VMs, the classic topo is something like: | VM1 | HOST | VM2 | app <- device -> qemu <- pmd -> l3fwd <- pmd -> qemu <- device -> app J.J. Martzki, Best wishes. Dinesh Kumar =E4=BA=8E2023=E5=B9=B44=E6=9C=8814=E6= =97=A5=E5=91=A8=E4=BA=94 01:32=E5=86=99=E9=81=93=EF=BC=9A > > Hello Experts, > > I am trying to run the following scenario using l3fwd example in dpdk-sta= ble-21.11.2 release . > > The flow is : > > VM1 = VM2 > ns0->tap0->DPDK <---------------------> DPDK-> bind a dev= ice with IP > > > The first question I have for VM2: > I assigned IP to the device and can see eth and static ip address via 'i= p add ', then after binding it to dpdk, I can not see this information via = ip add because it is not controlled by kernel module. > Is there any way to see ip and ethernet address after binding to DPDK? > Is this process correct to assign IP and then device to DPDK? > > > on VM1: > After starting the DPDK application, I can see a tap0 device created in = kernel mode via 'ip add show'.Then I attached this interface with network n= amespace via: > > ip netns add ns0 > ip link set tap0 netns ns0 > ip netns exec ns0 ip addr add dev tap0 > ip netns exec ns0 ip link set tap0 up > ip netns exec ns0 ip link set lo up > > Still, I am not able to ping anything from this ns0. > > Do I need any other configuration to ping via ns0 to VM2? > > Sorry, in case I am asking any dumb questions, I am new to DPDK and tryin= g to make the use case work. > Any help/pointer is really appreciated. > >