From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pa0-f48.google.com (mail-pa0-f48.google.com
 [209.85.220.48]) by dpdk.org (Postfix) with ESMTP id CFB7E8E61
 for <dev@dpdk.org>; Fri,  2 Oct 2015 02:03:53 +0200 (CEST)
Received: by padhy16 with SMTP id hy16so89047478pad.1
 for <dev@dpdk.org>; Thu, 01 Oct 2015 17:03:53 -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=iAqLhG0oWDH382aZg/LWLIUIFX65SV1TvL2hcL0XPcg=;
 b=GbosYqNY22eD1n4ZqbQQkBAmTyeS3Ux0OYoHBseBJcBTNBO1yj3F7xBYWyYhKvAF5i
 AWEoCCUsZNK8pgoSaUEzhTD36T487iE+BixYyv+g0Xd46rjLJCbmbitYpk9P/aIzsipO
 1orQai8EN/WAQBfoyfHD6SaGYDO2NKxb7MzRoqs7N9by5I/wFH0IG1OteybpBTJb4VN5
 7GICNqAOZp+Xzp4im0rlTmfCHfZXatpYfrVbapc3CbB8OCSOPLvfMA/DghiLQj7023iz
 Sr9nnuXcRBBQuyOmnkZXCmgn66dKg98Gm5exE5mQcr2I1stR4mu9I9wDFDA5yBbQyvbq
 GleA==
X-Gm-Message-State: ALoCoQmQvVMU0MWioSbcGBBxZUrZu2YRLUCPJZfROCciciHdtwmEH0fWOwEl1RM9XXzu0v/+8RRF
X-Received: by 10.68.190.105 with SMTP id gp9mr15750151pbc.152.1443744233120; 
 Thu, 01 Oct 2015 17:03:53 -0700 (PDT)
Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net.
 [50.53.82.155])
 by smtp.gmail.com with ESMTPSA id jo5sm8927495pbc.5.2015.10.01.17.03.52
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Thu, 01 Oct 2015 17:03:52 -0700 (PDT)
Date: Thu, 1 Oct 2015 17:04:03 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: Alexander Duyck <alexander.duyck@gmail.com>
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
Cc: dev@dpdk.org, Avi Kivity <avi@scylladb.com>, hjk@hansjkoch.de,
 gregkh@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [dpdk-dev] [PATCH 0/2] uio_msi: device driver
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2015 00:03:54 -0000

On Thu, 1 Oct 2015 16:43:23 -0700
Alexander Duyck <alexander.duyck@gmail.com> 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.