From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw1-f65.google.com (mail-yw1-f65.google.com [209.85.161.65]) by dpdk.org (Postfix) with ESMTP id 91B541B450 for ; Fri, 15 Feb 2019 03:16:53 +0100 (CET) Received: by mail-yw1-f65.google.com with SMTP id u205so3172196ywe.1 for ; Thu, 14 Feb 2019 18:16:53 -0800 (PST) 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; bh=pw9ZcfK2F21S6mHgImcBTmSNKUWI+LDORl1B1jN51zs=; b=fhkuhHSZwk5P/3GQLmNR7fHoGPUhu9HTVe9GCl0s6jVLYsf6/IXwP1D/eR9tB8QuM1 aCLkmP9e7777e+CDIJKpeIJiI5bgLTftedgdgRuILgPGbrLjEqpadZs9LpQjbqG7cICG C1bA3XZCBJxy7cN2e/wcCVg6kAj+j62hlKfmkWZ+5waNr094KicGRy8pZydZHzSA4IVT oeWHYzQM6XhlPUm4de8790eiT+07fJddZtxy/bYTJzUDU80+HBy3j7YW7A3uAAM7tDzJ flJDGkR6xpRb1e1wPUg/vDZjmsN37jZfNFxuAQpuFmmY06G5xycXH+AP8Y950Ylp7/2d xHlw== 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; bh=pw9ZcfK2F21S6mHgImcBTmSNKUWI+LDORl1B1jN51zs=; b=TWrpcmls+CwSmMFtX5HdSt4waWHI7myReaaMYOAvgS9oI6qWE6IEJMfQ6h6oeIRZQt asTSIxcA9cjeOb2ZEbNmlfGrpF5fPnPl0n/te/hTTPqU72c29dipv8dclskLB/wNWd9Q Evrcx7bbJl9J8+cn80suixA+Q3u047WCjhXUMpfzwxVNFC9YWbMK0hiaWebW6XODF039 5jBKeYzgfJQrTRD5VCS1Gc2YTVP9NQdD/44+3n06RVlKzMk+ynpMcusX9Uy08EAttPNG 3yl/CSvqayvP8xXEaf9EKTzZDnY8enmQT0TxTalE+o5kMXdDmQ2lHrLOew/ymGrAv59x n69w== X-Gm-Message-State: AHQUAubQSMflYRBhTMSqeRHjnNdeaaVmK3xa3WMgxc3RS6csvUQd5KYV ZKu6UXNmUUZzNkneb6bmE4/akBp1CXpLljLo6BaDtQ== X-Google-Smtp-Source: AHgI3IYY8iN05Io6lFE9JjWbChsGYimNyKtDtZQkBWXJVtY3pb16sFJ2vRHqBvWtRJuXt3F6y6qYKFEL5H7WQIkhJVs= X-Received: by 2002:a81:ad27:: with SMTP id l39mr6016508ywh.301.1550197012675; Thu, 14 Feb 2019 18:16:52 -0800 (PST) MIME-Version: 1.0 References: <20190214181115.416fddc8@shemminger-XPS-13-9360> In-Reply-To: <20190214181115.416fddc8@shemminger-XPS-13-9360> From: Cliff Burdick Date: Thu, 14 Feb 2019 18:16:41 -0800 Message-ID: To: Stephen Hemminger Cc: users Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Mellanox + DPDK + Docker/Kubernetes X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2019 02:16:53 -0000 This is bare metal (PF). I actually traced down where it's failing in the mellanox driver -- it's doing an ioctl with the name of the interface, and that call fails since the devices aren't visible to the application (not in /proc/net/dev). Although, the mellanox driver did successfully pull the name from the ib driver. I think this is probably just not possible without something like multus to support multiple devices in an unofficial way. I'm assuming this would actually work with Intel NICs since they aren't visible to the kernel as a regular net device at all, and thus wouldn't need ioctl. On Thu, Feb 14, 2019, 18:11 Stephen Hemminger On Thu, 14 Feb 2019 13:05:28 -0800 > Cliff Burdick wrote: > > > Hi, I'm trying to get DPDK working inside of a container deployed with > > Kubernetes. It works great if I pass hostNetwork: true (effectively > > net=host in Docker) to where the container sees all the host interfaces. > > The problem with this is you lose all normal Kubernetes networking for > > other non-DPDK interfaces by doing this. If I disable host networking, I > > get the following error: > > > > EAL: Probing VFIO support... > > EAL: PCI device 0000:01:00.0 on NUMA socket 0 > > EAL: probe driver: 15b3:1013 net_mlx5 > > net_mlx5: port 0 cannot get MAC address, is mlx5_en loaded? (errno: No > such > > device) > > net_mlx5: probe of PCI device 0000:01:00.0 aborted after encountering an > > error: No such device > > EAL: Requested device 0000:01:00.0 cannot be used > > > > I've tried mounting /sys and /dev in the container from the host, and it > > still doesn't work. Is there something I can do to get the Mellanox mlx5 > > driver to work inside a container if it can't see the host interfaces? > > Is this Mellanox on bare-metal (ie PF). > Or Mellanox VF as used in Hyper-V/Azure? > >