From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Allain.Legacy@windriver.com>
Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13])
 by dpdk.org (Postfix) with ESMTP id 786BFFC1E
 for <dev@dpdk.org>; Thu, 30 Mar 2017 00:45:59 +0200 (CEST)
Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com
 [147.11.189.40])
 by mail1.windriver.com (8.15.2/8.15.1) with ESMTPS id v2TMjvhI010924
 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL);
 Wed, 29 Mar 2017 15:45:57 -0700 (PDT)
Received: from ALA-MBC.corp.ad.wrs.com ([fe80::fcbe:9b7:1141:89a1]) by
 ALA-HCA.corp.ad.wrs.com ([147.11.189.40]) with mapi id 14.03.0294.000; Wed,
 29 Mar 2017 15:45:56 -0700
From: "Legacy, Allain" <Allain.Legacy@windriver.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
CC: "mtetsuyah@gmail.com" <mtetsuyah@gmail.com>, "maxime.coquelin@redhat.com"
 <maxime.coquelin@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>, "Peters, Matt"
 <Matt.Peters@windriver.com>, Thomas Monjalon <thomas.monjalon@6wind.com>
Thread-Topic: [PATCH] vhost: change mbuf allocation logs to debug
Thread-Index: AQHSp4+zZeFE6H7K2EablnK89acMGaGqH/+ggAG65wCAAJF4kA==
Date: Wed, 29 Mar 2017 22:45:55 +0000
Message-ID: <70A7408C6E1BFB41B192A929744D8523968FA875@ALA-MBC.corp.ad.wrs.com>
References: <20170327162930.54281-1-allain.legacy@windriver.com>
 <20170328064841.GZ18844@yliu-dev.sh.intel.com>
 <70A7408C6E1BFB41B192A929744D8523968F8CC8@ALA-MBC.corp.ad.wrs.com>
 <20170329070150.GF18844@yliu-dev.sh.intel.com>
In-Reply-To: <20170329070150.GF18844@yliu-dev.sh.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [128.224.140.166]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-dev] [PATCH] vhost: change mbuf allocation logs to debug
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, 29 Mar 2017 22:46:00 -0000

> -----Original Message-----
> From: Yuanhan Liu [mailto:yuanhan.liu@linux.intel.com]
> Sent: Wednesday, March 29, 2017 3:02 AM

<...>
>=20
> OTOH, it's still good to have RTE_LOG_ONCE. It explicitly tells you somet=
hing
> is wrong, then you could dump those stats for more info.

Has the implementation of something like RTE_LOG_ONCE been discussed before=
? =20

Do you have a proposal on what you would find acceptable as an implementati=
on that considers multiples threads, multiple devices, multiple logs per fi=
le, etc.?