From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id AAE6DA317C for ; Thu, 17 Oct 2019 13:28:55 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 38AFE1E95A; Thu, 17 Oct 2019 13:28:54 +0200 (CEST) Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by dpdk.org (Postfix) with ESMTP id 377C51E950 for ; Thu, 17 Oct 2019 13:28:52 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1308; q=dns/txt; s=iport; t=1571311733; x=1572521333; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=gmGA5n0X1PdzklZiTmOr/XlOyRwES2sdwADgN2cvD5c=; b=k17mEdhMIqAy29QyUbbA5wO80u6ilGA6V32vNXJM0oq78mhNEqoi37vX stVFgw4wGxEPV08tImKXtus9wQ1p9E7pHloXbsChSNbNvGu98Ln9PoVC1 j1qbNCMaSjDmtZEADiwIkD9kFFr6N6bpk4MSoJ5fbNjec58ZxdUEe+y4h 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BEAADsT6hd/5JdJa1lGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBEQEBAQEBAQEBAQEBgXuCIIFyKgqVEpsoCQEBAQwBAS8BAYR?= =?us-ascii?q?AAoMDJDgTAgMJAQEEAQEBAgEFBG2FOYVLAQEBBCcTPwwEAgEIEQQBAR8QMh0?= =?us-ascii?q?IAgQOBQiGEq5XgXQzikSBNIwOGIF/hCM+ijAErVEKHYIFlRkjmUanbgIRFYE?= =?us-ascii?q?yNyKBWHAVgydQEBSQFkMxkBuBIwEB?= X-IronPort-AV: E=Sophos;i="5.67,307,1566864000"; d="scan'208";a="351407276" Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 17 Oct 2019 11:28:51 +0000 Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x9HBSpHg000720 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 17 Oct 2019 11:28:51 GMT Received: from xch-aln-004.cisco.com (173.36.7.14) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 17 Oct 2019 06:28:51 -0500 Received: from xch-aln-004.cisco.com ([173.36.7.14]) by XCH-ALN-004.cisco.com ([173.36.7.14]) with mapi id 15.00.1473.003; Thu, 17 Oct 2019 06:28:51 -0500 From: "Jakub Grajciar -X (jgrajcia - PANTHEON TECHNOLOGIES at Cisco)" To: Anand Sunkad CC: "dev@dpdk.org" , Vivek Gupta , Thomas Mulamangalath Thread-Topic: [PATCH] net/memif: add multiple memif data transmission support Thread-Index: AQHVhCS3QhB6QP0RNke/c6zAlcP55ades0hw Date: Thu, 17 Oct 2019 11:28:51 +0000 Message-ID: References: <1571232181-5874-1-git-send-email-anand.sunkad@benisontech.com> In-Reply-To: <1571232181-5874-1-git-send-email-anand.sunkad@benisontech.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.61.79.248] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com X-Outbound-Node: rcdn-core-10.cisco.com Subject: Re: [dpdk-dev] [PATCH] net/memif: add multiple memif data transmission support X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > -----Original Message----- > From: Anand Sunkad > Sent: Wednesday, October 16, 2019 3:22 PM > To: Jakub Grajciar -X (jgrajcia - PANTHEON TECHNOLOGIES at Cisco) > > Cc: dev@dpdk.org; Vivek Gupta ; Thomas > Mulamangalath ; Anand Sunkad > > Subject: [PATCH] net/memif: add multiple memif data transmission support >=20 > When Multiple slave/master Memif interfaces are created in single process > data transmission over second connection is not successful. >=20 > Issue is because of "mq->in_port" is not initialized with "dev->data->por= t_id" > in memif_msg_enq_add_ring() and > memif_msg_receive_add_ring() functions, and while transmitting packets > over second connection in eth_memif_tx function it refer "mq->in_port" > which is always zero, and leads to data transmission always in 0th port. >=20 > To mitigate the issue,"mq->in_port" is initialized with "dev->data->port_= id" in > memif_msg_enq_add_ring() and > memif_msg_receive_add_ring() functions. >=20 > Signed-off-by: Anand Sunkad Good catch, however you want to initialize mq->in_port in memif_tx_queue_se= tup(). Thanks, Jakub