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 7BCECA3295 for ; Wed, 23 Oct 2019 10:45:37 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 423741BFDB; Wed, 23 Oct 2019 10:45:37 +0200 (CEST) Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by dpdk.org (Postfix) with ESMTP id B27911BFD2 for ; Wed, 23 Oct 2019 10:45:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1176; q=dns/txt; s=iport; t=1571820335; x=1573029935; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=lRiN2LpsmgXYAEjWqXoPzLXMP6P4ldX+w5nyC5WMdnA=; b=OvAN75m4quBsq76oIqWixJwXe8up13dM32zFjIkkLiB5wyOuWyRuhbvm +Tb6j2KuRyV559knnXGBTC6DxGBie7f2YBVewkKoyihPaFzMwAittj0sT rVeWGAxWinH9nPcQrEHAOkDrAJNqIP44W6zfBd6TxVFCdEFkfQBYEfgRi 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BEAACvErBd/51dJa1lGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBEQEBAQEBAQEBAQEBgXuCIIFyKgqVGZsrCQEBAQwBAS8BAYR?= =?us-ascii?q?AAoMyJDgTAgMJAQEEAQEBAgEFBG2FQ4VLAQEBAQMnEz8MBAIBCBEEAQEfEDI?= =?us-ascii?q?dCAIEDgUIhhKwdoF0M4pFgTaMDxiBf4QjPoozBK1eCh2CB5UeI5lOp30CERW?= =?us-ascii?q?BMjcigVhwFYMnUBAUkUxDMY5/gSQBAQ?= X-IronPort-AV: E=Sophos;i="5.68,220,1569283200"; d="scan'208";a="348925292" Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Oct 2019 08:45:33 +0000 Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x9N8jXeQ016458 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 23 Oct 2019 08:45:33 GMT Received: from xch-aln-004.cisco.com (173.36.7.14) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 23 Oct 2019 03:45:33 -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; Wed, 23 Oct 2019 03:45:33 -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/c6zAlcP55ade02SAgAkgFFA= Date: Wed, 23 Oct 2019 08:45:32 +0000 Message-ID: <6949a19b9c554cddbc11554ad771c234@XCH-ALN-004.cisco.com> References: <1571232181-5874-1-git-send-email-anand.sunkad@benisontech.com> <1571318513-7100-1-git-send-email-anand.sunkad@benisontech.com> In-Reply-To: <1571318513-7100-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.192.224] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com X-Outbound-Node: rcdn-core-6.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: Thursday, October 17, 2019 3:21 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's 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->port_id" in memif_tx_queue_setup() function, and while > transmitting packets over second connection in eth_memif_tx function > it refer "mq->in_port" which is always zero, which 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_tx_queue_setup() function. >=20 > Signed-off-by: Anand Sunkad Reviewed-by: Jakub Grajciar