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 BAD8FA04F2; Mon, 30 Dec 2019 11:51:48 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 084A91C0D4; Mon, 30 Dec 2019 11:51:48 +0100 (CET) Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50050.outbound.protection.outlook.com [40.107.5.50]) by dpdk.org (Postfix) with ESMTP id 96B401C0C5 for ; Mon, 30 Dec 2019 11:51:46 +0100 (CET) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SkonIojrVqu00TxTSDh4kD7cxM0fNwsb/5kxxaTwLTOtdkfGzTc7FZDtcpCgDPXIZUHF7I9T9nxDhl3b7N3ZneKmgx/UXcCTG6+PqxKkODR8222LSA9VqiWgv9q9CnmA8M4mOu3xIOgBiY9WzzTT1quzBC9LUAS1by87dbeVC3MrZyYyQf2BfjYzQyXV9m1q8XfP02XQy1ujmTO4eM9vgI2CVXvcTmr6pxE3qIde4966kwpK3dnj1Wdv2qxmKpTI11pwO37zC/aDK+erihqCs+kQtXAUxnf1dO58dfpvPAiKJmGBoYr2Ak/6ZJo7AGrs9y5DPF82zEzug0MaHbw9ng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=m9uXXWcdZ8FyH3Buqfl7PH7eaFNbwhoZ2T1Nk8hkbs4=; b=kKo/G42AD7BOw3C5fSWHCiUCOaj6M/E2cdoWgwyZ0c5POZo2iDvJvuFcgmER38BcEmN2keZCdV87FC7hF0xzg8A2ZyQbcgr0p1PzqvIqvLZ7OiuQftL42ZiVeiuNdUQjiSKMUXX6VoQWHTD/gVJiHMgEBmOn7vLtwejBtVWqzi9n5GoVjoA+VHxJPuT7VKQLsN/+bYpjIRHb1l0tO+Ib3QHWOl1OYMaclfzzHSHcEYF6cz8IaLTnEuYePLplsSVCKMQnrM5R+AmREwctg4rhK9/q9rW3GZlY2nT6UxvT736I3U9iKr3JZODn7JPLz/ZP6nYkGtGEMu2o/y8ZjlnS9w== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=m9uXXWcdZ8FyH3Buqfl7PH7eaFNbwhoZ2T1Nk8hkbs4=; b=HHISuWadSdti4w0JcUxji2f0qvIhVrXNERUUMtfUt4hhKYvXSqJsM+RohIYJAhwQpaMf4op1qyac3qcVSXdWIA6HS4lZo+JQyt48Yl+R1vQGwFYWwJEnSkKLxM24fkb3jUsS8IrK5hnnQ9uUfFaArRoJ8vw+HhF98+Dgs3GkfcM= Received: from AM6PR07MB4069.eurprd07.prod.outlook.com (52.134.116.150) by AM6PR07MB4759.eurprd07.prod.outlook.com (20.177.37.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2602.9; Mon, 30 Dec 2019 10:51:45 +0000 Received: from AM6PR07MB4069.eurprd07.prod.outlook.com ([fe80::8c06:cf20:6a4c:a5de]) by AM6PR07MB4069.eurprd07.prod.outlook.com ([fe80::8c06:cf20:6a4c:a5de%6]) with mapi id 15.20.2602.010; Mon, 30 Dec 2019 10:51:45 +0000 From: =?Windows-1252?Q?Mattias_R=F6nnblom?= To: Liron Himi CC: Yuri Chipchev , Jerin Jacob Kollanukkaran , dpdk-dev Thread-Topic: l2fwd-event not fully functional with 'dsw' Thread-Index: AdW+eZcEuNEOcUqWTCaklj2wsWyg3QAhYj4A Date: Mon, 30 Dec 2019 10:51:44 +0000 Message-ID: <10db7a38-407f-9d9f-b0ab-826e0787a8fa@ericsson.com> References: In-Reply-To: Accept-Language: sv-SE, en-US Content-Language: sv-SE X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 authentication-results: spf=none (sender IP is ) smtp.mailfrom=mattias.ronnblom@ericsson.com; x-originating-ip: [192.176.1.85] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: f3ef0c0c-7926-4f0a-6792-08d78d164315 x-ms-traffictypediagnostic: AM6PR07MB4759: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-forefront-prvs: 0267E514F9 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(376002)(346002)(136003)(39860400002)(396003)(189003)(199004)(6512007)(81166006)(81156014)(8936002)(8676002)(71200400001)(53546011)(6486002)(6506007)(6916009)(26005)(36756003)(66446008)(2616005)(64756008)(66556008)(66476007)(66946007)(186003)(4326008)(478600001)(2906002)(316002)(4001150100001)(31686004)(5660300002)(54906003)(86362001)(76116006)(31696002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM6PR07MB4759; H:AM6PR07MB4069.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: aWPD/zNAHKXTQ+69AL4vYLUS33T0XKPsHYOXIESeNJuNPWVF40STqYKMrXKYXwWV/9lKLdlAl9PjHX2oGIQyR+xqkehJW2wf5xKi0mejozSLjOHkWynjeXvNPqzuD0Sl0w87uLqGLAt90kFmHUtSyzpGBlRZJc8cMKrv2pMxNcU23h8G/XDY6BsO6psNrw1qkYB3etmEyTyHvGIqxhyHdh+V2ZUFN14TOiyX8mVOViiM633DDWGG5U3TOQCexuCmVchWIvfqovbnSO8na6AczE7R0UEuDhmsQR6TSMFRXJPtM+6fH4AZmLZEPsy8nGSaERzxdKdJKWmlk1BgFFL+NA7QGEl4LPYdooH1w0Ow7GGpYvHCXHp2388Fqv2GoDd5tiXcurawKBEeW4sbY58rjC0G2uWFOsD/mQ7DXnTPUuSeOLeCRtpg2Sp0GJ+xX3LO x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="Windows-1252" Content-ID: <2D521DC6E3082940AE72C91468393D5C@eurprd07.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: ericsson.com X-MS-Exchange-CrossTenant-Network-Message-Id: f3ef0c0c-7926-4f0a-6792-08d78d164315 X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Dec 2019 10:51:44.9778 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: d/kOkOMfaAsmkoH9FekWgFfGZ/n6dV2lMHnPXvAbP6HbEV8sx+GdyW5/0VvtNZ9eD+8XByQT+ZmHcjP+Lfy22KDXzW7m9dSxm29PKF36EhY= X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR07MB4759 Subject: Re: [dpdk-dev] l2fwd-event not fully functional with 'dsw' 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" On 2019-12-29 20:45, Liron Himi wrote: > > Recently we tried to run the new l2fwd-event examples using the =91dsw=92= =20 > as the evendev. > > We noticed that only 4096 packets were sent back to the ethdev. > > Only when we changed both =91dequeue_depth=92 and =91enqueue_depth=92 to = 128=20 > instead of 32, it started to work. > > Do you have any objections for modifying =A0the =91dsw=92 default=20 > configuration to =91128=92? > I suspect the problem isn't really the default dsw burst sizes, but=20 rather the additional requirements that dsw puts on its user. In=20 particular, the requirement that no eventdev ports may be left "unattended"= . From what I can see, l2fwd-event uses the rx ethernet adapter. In case=20 there are no ingress packets, the rx ethernet adapter will leave its=20 eventdev port unattended, and thus will not work properly with dsw. If someone wants to explore if this is indeed the problem, they could=20 try adding a zero-sized rte_event_dequeue_burst() (being called for=20 every service invocation) in the rx adapter code. A dequeue call will=20 allow the dsw flow migration machinery to function properly, and will=20 also periodically flush buffered events.A zero-sized enqueue operation=20 (as suggested by the dsw documentation) would also work, but that would=20 have the side-effect of always flushing any buffered events, which might=20 be non-optimal from a performance point of view. The same might also hold true for the l2fwd-event code, but at least the=20 burst-variant of the main loop will periodically attend the eventdev=20 port (by means of a dequeue and/or enqueue). The proper way to address this issue would probably be to add a "needs=20 maintenance" capability flag, and a pure event device maintenance=20 function added to the eventdev API, or something along those lines.=20 Another way might be to use a dsw-internal per lcore timer. That would=20 instead require the user to call rte_timer_manage(). An additional=20 complication for the latter solution is that, even though an eventdev=20 port is not thread-safe, it doesn't really have an "owning" lcore, and=20 thus it's difficult to figure out on which lcore to install the timer.