From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 41ABAA0547; Wed, 21 Apr 2021 15:21:22 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 209E841AC8; Wed, 21 Apr 2021 15:21:22 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id D2ACE410F9 for ; Wed, 21 Apr 2021 15:21:20 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1619011280; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=j/D9IV/k95jHEf4e4y7+EGUvOuE9uT6Qg3rnsgRpGBE=; b=gWMsvDjehWEgX3y0uLNBwI7yf/57Xwvph1nwf55TN25M71HYdChwvpkjriU1ekNM+8yHUe XnYVS3RNDYdPx630S/+DO6CLOd3aktUkwTQkoQmidrKdFOB6A2bB34So14tBtsQZ8lB/ew VRWYMuRc2RazWV4AVrn3tg6OKm37hfM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-130-O3PBBjw0NQOg8rbxUeJsNw-1; Wed, 21 Apr 2021 09:21:16 -0400 X-MC-Unique: O3PBBjw0NQOg8rbxUeJsNw-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D4DA819251D3; Wed, 21 Apr 2021 13:21:07 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (ovpn-115-145.rdu2.redhat.com [10.10.115.145]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 278C85C1B4; Wed, 21 Apr 2021 13:21:07 +0000 (UTC) From: Aaron Conole To: Ali Alnubani Cc: NBU-Contact-Thomas Monjalon , Cristian Dumitrescu , "dev\@dpdk.org" References: <20210411232338.4005-1-cristian.dumitrescu@intel.com> <20210411232338.4005-2-cristian.dumitrescu@intel.com> <2003889.D9zfWNbQnx@thomas> Date: Wed, 21 Apr 2021 09:21:06 -0400 In-Reply-To: (Ali Alnubani's message of "Wed, 21 Apr 2021 13:03:31 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=aconole@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Subject: Re: [dpdk-dev] [PATCH 2/2] pipeline: autodetect endianness of action args X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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" Ali Alnubani writes: >> -----Original Message----- >> From: Aaron Conole >> Sent: Wednesday, April 21, 2021 3:57 PM >> To: Ali Alnubani >> Cc: NBU-Contact-Thomas Monjalon ; Cristian >> Dumitrescu ; dev@dpdk.org >> Subject: Re: [dpdk-dev] [PATCH 2/2] pipeline: autodetect endianness of >> action args >> >> Ali Alnubani writes: >> >> > Hi, >> > >> >> -----Original Message----- >> >> From: dev On Behalf Of Thomas Monjalon >> >> Sent: Tuesday, April 20, 2021 10:58 PM >> >> To: Cristian Dumitrescu >> >> Cc: dev@dpdk.org >> >> Subject: Re: [dpdk-dev] [PATCH 2/2] pipeline: autodetect endianness of >> >> action args >> >> >> >> 12/04/2021 01:23, Cristian Dumitrescu: >> >> > Each table entry is made up of match fields and action data, with the >> >> > latter made up of the action ID and the action arguments. The approach >> >> > of having the user specify explicitly the endianness of the action >> >> > arguments is difficult to be picked up by P4 compilers, as the P4 >> >> > compiler is generally unaware about this aspect. >> >> > >> >> > This commit introduces the auto-detection of the endianness of the >> >> > action arguments by examining the endianness of the their destination: >> >> > network byte order (NBO) when they get copied to headers and host >> byte >> >> > order (HBO) when they get copied to packet meta-data or mailboxes. >> >> > >> >> > The endianness specification of each action argument as part of the >> >> > rule specification, e.g. H(...) and N(...) is removed from the rule >> >> > file and auto-detected based on their destination. The DMA instruction >> >> > scope is made internal, so mov instructions need to be used. The >> >> > pattern of transferring complete headers from table entry action args >> >> > to headers is detected, and the associated set of mov instructions >> >> > plus header validate is internally detected and replaced with the >> >> > internal-only DMA instruction to preserve performance. >> >> > >> >> > Signed-off-by: Cristian Dumitrescu >> >> >> >> Series applied, thanks >> >> >> >> >> > >> > I believe this patchset is causing the build failures in >> https://bugs.dpdk.org/show_bug.cgi?id=683. >> >> Where do you see those build errors? Compiler version, etc? For example: >> >> https://github.com/ovsrobot/dpdk/actions/runs/767327010 >> >> This build was successful after rerunning with the prerequisite patch >> applied to mainline. I am concerned why the CI didn't catch this. >> > > From the ticket: >> OS: CentOS 7.9.2009 >> gcc: 4.8.5 >> meson: 0.55.1 >> ninja-build: 1.10.2 > > The build errors don't reproduce in Ubuntu 18.04. Thanks. > - Ali