From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751281AbbJBADz (ORCPT ); Thu, 1 Oct 2015 20:03:55 -0400 Received: from mail-pa0-f44.google.com ([209.85.220.44]:33196 "EHLO mail-pa0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750963AbbJBADx (ORCPT ); Thu, 1 Oct 2015 20:03:53 -0400 Date: Thu, 1 Oct 2015 17:04:03 -0700 From: Stephen Hemminger To: Alexander Duyck Cc: Avi Kivity , dev@dpdk.org, hjk@hansjkoch.de, gregkh@linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [dpdk-dev] [PATCH 0/2] uio_msi: device driver Message-ID: <20151001170403.1ba4dad3@urahara> In-Reply-To: <560DC51B.7030507@gmail.com> References: <1443652138-31782-1-git-send-email-stephen@networkplumber.org> <560D11F6.2080609@scylladb.com> <20151001075731.2f079237@urahara> <560D8E14.5030500@gmail.com> <20151001150036.7a20b228@urahara> <560DBBAA.3050906@gmail.com> <20151001163918.1bc98774@urahara> <560DC51B.7030507@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 1 Oct 2015 16:43:23 -0700 Alexander Duyck wrote: > Yes, but in the case of something like a VF it is going to just make a > bigger mess of things since INTx doesn't work. So what would you expect > your driver to do in that case? Also we have to keep in mind that the > MSI-X failure case is very unlikely. > > One other thing that just occurred to me is that you may want to try > using the range allocation call instead of a hard set number of > interrupts. Then if you start running short on vectors you don't hard > fail and instead just allocate what you can. I tried that but the bookkeeping gets messy since there is no good way to communicate that back to userspace and have it adapt.