From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f170.google.com (mail-pf1-f170.google.com [209.85.210.170]) by dpdk.org (Postfix) with ESMTP id 3A8A169D4 for ; Thu, 25 Oct 2018 18:45:42 +0200 (CEST) Received: by mail-pf1-f170.google.com with SMTP id a15-v6so650802pfn.0 for ; Thu, 25 Oct 2018 09:45:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=j/6dNvsVzDsa3sKMh5wcQR/RWtXJt8OwG7xzD0hbVpg=; b=zx7gmlG3ThAb3/x88teb/Ll22t0Dw6EuC9jWGzUaHgdE6dLouY/an/44Ey6Wo0eBw8 7zm+bFksWLvHcOzj55jjUrvQjLXV/TwSWSZ5MdSg/ZpX3IQiuW9qwYzbCt7OAK3QWxV5 cLRdDOMx7tGcztvs8dr7lP8DVzYEAhl/ItfVqwlxpyDfmCMMoesBQ3mAmq9pDRM/4KCJ u0UBlmuRVdNZpkLbwgkQFvlzWr+6+klmjuU02hUa1lK9QOWEqRgxE0Js8hNH5kFn1jFn UVS5jIQbze2OxXhVkrZ2j957NQvJn7AiUWAtI9WwMF8/s3yXfdXX9NsFcJSFtML/BMIU ZqwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=j/6dNvsVzDsa3sKMh5wcQR/RWtXJt8OwG7xzD0hbVpg=; b=n9011jl64uS0B254pPQlvBDT/JmS0Ou8D6HK6LldMAqkfuHw4LvdYpBU30PGiVzJ04 /Z49a/2dWF+RAr/VCKXzvCvHZS2PDGv8PS3RJS5iJBpF/aTa1l464E1xVWuPG987k9fW SrYhexagkPbJNYJDWROU9IJh47upuoTJSF3lU5g7f+iREX377Low1lKbaFKivs6RX6Dm +0qSnS/ILucpWLcjm5I7lXp9iJ9P3pt2Pn5E8B3v9szEUODMf7JCFGqXp4hlMJIUiXA5 D8bb7FYY7TY8ATlFqz3XAGNs80c8fq3M1mFAnv2hkGSwSJB/dGzX++5C4MhMQ7l774Bz 0cSw== X-Gm-Message-State: AGRZ1gJj3ezBT8avDovse3iax65EmjcqicVOrhknMTsy/AZFiqTjl6wc CjZj8QZ2fLRBJaSmaJZwcoR2MQ== X-Google-Smtp-Source: AJdET5cYgqtCpcDYhitaOfAeGpVxNc7zkb1JFj5L2sSbvMkuFqZmA25wrGCFbXKg9H8+nYEOA5O3Lg== X-Received: by 2002:a63:eb42:: with SMTP id b2-v6mr2121452pgk.348.1540485941125; Thu, 25 Oct 2018 09:45:41 -0700 (PDT) Received: from xeon-e3 (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id l7-v6sm1881852pgb.22.2018.10.25.09.45.40 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 25 Oct 2018 09:45:41 -0700 (PDT) Date: Thu, 25 Oct 2018 09:45:33 -0700 From: Stephen Hemminger To: siddharth verma Cc: users@dpdk.org, dev@dpdk.org, users-request@dpdk.org Message-ID: <20181025094533.01a7a6ef@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] Regarding -:[dpdk-dev] net_vmxnet3: link status Interrupt is not working in DPDK 17.11.2 version 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: Thu, 25 Oct 2018 16:45:42 -0000 On Thu, 25 Oct 2018 16:52:07 +0530 siddharth verma wrote: > Hi , > link status Interrupt is not working in DPDK 17.11.2 version for > net_vmxnet3 driver , we are doing port connect/disconnect using vmware/ESXI > but we are getting any LSI from DPDK. Looks like dpdk is not generating any > event . > > > > Please do let me know, whether I am missing any configuraion/patch ? Any > help would be appreciated > > Please stop resending this mail. I am sure if the vmxnet3 maintainer is watching this list they heard you the first time. You might have better luck looking up the maintainer of that device in the source and mailing directly.