From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f48.google.com (mail-pa0-f48.google.com [209.85.220.48]) by dpdk.org (Postfix) with ESMTP id 9261B3237 for ; Wed, 15 Apr 2015 18:38:24 +0200 (CEST) Received: by pabtp1 with SMTP id tp1so56555622pab.2 for ; Wed, 15 Apr 2015 09:38:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=UBAlJkIl/YhUr/QHf9yeUZ4REYquD6H7cJ0sx7w7nm4=; b=hBZFSKj6IhMhK2Q+OwaSEjlEFsn5m0r+qaUIQkvThuQsz/SblMnDWjPe1dZ2lxREld mdcFnxvzdIJDab3spYbJIckuBOLZiaIpS16nGSPg+ANpdDJpgX3ueXm7cTRf4aGK7gTi naQ1UtWsJgTrhztYqoY3Axcyx2jys9/koQo1EpzCvtDqWzAhXO4jWwJFgAVuSKYXtxYp WJH2PSBzkQOilqyezoiQGUCUAXUzFN5h6aK0wIFNMDGhFDGNqSDdqKkfszgF5kgXHEl9 /8Uziy2JDyaUriRybkQx34SFWhE5c17BLw/NxI9+gEqjMRqvoFn17ZWs9uMdztY2Os0B OOvQ== X-Gm-Message-State: ALoCoQmYCWBTQHeJ0yaxftkNNc3XtSuRScgSH49WHCQtn3uNUgxtKLYN2zqyBGrZs9H3X9UHEBn/ X-Received: by 10.66.101.9 with SMTP id fc9mr47334415pab.37.1429115903902; Wed, 15 Apr 2015 09:38:23 -0700 (PDT) Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net. [50.53.82.155]) by mx.google.com with ESMTPSA id np6sm4599573pdb.80.2015.04.15.09.38.23 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Apr 2015 09:38:23 -0700 (PDT) Date: Wed, 15 Apr 2015 09:34:20 -0700 From: Stephen Hemminger To: "Zhou, Danny" Message-ID: <20150415093420.6fc93b76@urahara> In-Reply-To: References: <20150414180620.03deb8ee@urahara> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" Subject: [dpdk-dev] [PATCH 0/2] fix UIO support broken by 2.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 16:38:25 -0000 Here is the correct way to fix it (even if it maybe hard to accept). I think the most technically correct way to handle this is to fix UIO driver in kernel to do the IRQ management according to the API that was already described in the kernel documentation. Then have the DPDK EAL use the IRQ management API. This maybe hard for Enterprise distributions to accept, but it is the right technical solution.