From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id B522E2BBB
 for <dev@dpdk.org>; Wed,  7 Jun 2017 16:23:10 +0200 (CEST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 493BB208B8;
 Wed,  7 Jun 2017 10:23:10 -0400 (EDT)
Received: from frontend1 ([10.202.2.160])
 by compute1.internal (MEProxy); Wed, 07 Jun 2017 10:23:10 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:content-transfer-encoding:content-type:date:from:in-reply-to
 :message-id:mime-version:references:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=jLquwysEl5PrFyE
 gGPBjPMO4fSrrOgda9z6g2Jhxbrk=; b=H5vRt/VgNcfY/oN1b9n+Ss/FKYKj7pH
 u+albZvB+DhKxKKXgvBRzzLmfQJte35ScLzg4UZoEYu/FdDtumMYhu4BSIJTRJmm
 cMOB8K+8/HsA/Yzx5q+q2niNMkA3V/w3bCg56I4VX4qe0G/hOGLkNJskzhbaCvXv
 IWLuC8lpWMY0=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s=
 fm1; bh=jLquwysEl5PrFyEgGPBjPMO4fSrrOgda9z6g2Jhxbrk=; b=RMwNIgCS
 Xg3XopnOGufDxQWfiIvKRDvGd5IhzTWokhfiueVuWzWC507urAyc4mdp1FqcTZJq
 3gZaDT9gQxiXAi1fdKggargwVVzxqjF7QmI0imP5oqm817DElbsE2lZBhbEYhJRT
 X6W3SiqY2b5o+uwWjgUNa0hG8NK1D8/xeUsGsEHg9IPezS7TBK0K0aexCpI1zKO1
 opa7tyBWP5F8g4qcQPkW44iFFXMx/S6YvQooDUEmsXTxrR9/OdhfjjFkiWMxQ7qQ
 7yd1VrOZF+CCtsIMtdJBmP+ynj0b5OgHKwFaWf7ulwHEIZq5vrCbvPLj7x4vfdxO
 gnj9Jdg/KxOv3w==
X-ME-Sender: <xms:Tgw4Wcb2QipMsYGaOCbuCtUwWh3ID9I_-_WmI_NwjH3X9OOjc-pPjQ>
X-Sasl-enc: YShFatNZIarAAN0glXhiCOggybnSGreX+xvrcyfPxy26 1496845389
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id EF4EA7E855;
 Wed,  7 Jun 2017 10:23:09 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Date: Wed, 07 Jun 2017 16:23:09 +0200
Message-ID: <4912406.Tfa8CUZAWC@xps>
In-Reply-To: <20170524164008.4d4e8e7b@xeon-e3>
References: <20170524164008.4d4e8e7b@xeon-e3>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] PCI domain size
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <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: Wed, 07 Jun 2017 14:23:11 -0000

25/05/2017 01:40, Stephen Hemminger:
> While working on SR-IOV support on Azure, it was discovered that some applications
> and drivers do not support full size PCI domains. On Azure environment the PCI pass
> through device has a synthetic domain value (ie generated by host) which is > 16 bits.
> 
> The common PCI utilities (pci-utils) and Linux kernel both support
> full 32 bits but DPDK does not. FreeBSD also supports 32 bit domains.
> 
> Changing the one place in DPDK (rte_pci.h) in source is trivial but of course
> it is a major ABI breakage which is a complete flag day. I.e no binary compatiabilty
> is possible.

I guess you are talking about
struct rte_pci_addr {
	uint16_t domain;
	uint8_t bus;
	uint8_t devid;
	uint8_t function;
};

I do not see why we would not change it to comply to the standard.
Do you want to propose a deprecation?