From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pavel Fedin <p.fedin@samsung.com>
Subject: Re: [PATCH v2 0/5] add dpdk packet capture support
	for	tcpdump
Date: Wed, 24 Feb 2016 18:04:57 +0300
Message-ID: <030301d16f14$ba106240$2e3126c0$@samsung.com>
References: <1455289045-25915-1-git-send-email-reshma.pattan@intel.com>
 <014201d16a55$d05e4b20$711ae160$@samsung.com>
 <3AEA2BF9852C6F48A459DA490692831FFC6353@IRSMSX109.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org
To: "'Pattan, Reshma'" <reshma.pattan@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mailout3.w1.samsung.com (mailout3.w1.samsung.com
 [210.118.77.13]) by dpdk.org (Postfix) with ESMTP id E7DEB298F
 for <dev@dpdk.org>; Wed, 24 Feb 2016 16:05:00 +0100 (CET)
Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245])
 by mailout3.w1.samsung.com
 (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014))
 with ESMTP id <0O3200NZ84KA0G30@mailout3.w1.samsung.com> for dev@dpdk.org;
 Wed, 24 Feb 2016 15:04:58 +0000 (GMT)
In-reply-to: <3AEA2BF9852C6F48A459DA490692831FFC6353@IRSMSX109.ger.corp.intel.com>
Content-language: ru
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

 Hello!

> >  2. What if i don't want separate RX and TX streams either? It only prevents me
> > from seeing the complete picture.
> 
> Do you mean not to have separate pcap files for tx and rx? If so, I would prefer to keep this
> as it is.

 I mean - add an option not to have separate files.

> Because pcap changes need to be replaced with TUN/TAP pmd once available in future.

 I believe it's lo-o-o-ong way to get there... 

> >  3. vhostuser ports are missing. Perhaps not really related to this patchset, i just
> > don't know how much code "server" part of vhostuser shares with normal PMDs,
> > but anyway, ability to dump them too would be nice to have.
> >
> 
> I think this can be done in future i.e. when vhost as PMD is available. But as of now vhost
> is library.

 I expected "server"-side vhost to be the same as "client" part (AKA virtio), just use another mechanism for exchanging control
information (via socket). Is it not true? I suppose, driving queues from both sides should be quite symmetric.

Kind regards,
Pavel Fedin
Senior Engineer
Samsung Electronics Research center Russia