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 4B4AFA00C4; Fri, 30 Sep 2022 10:34:53 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DC79140E5A; Fri, 30 Sep 2022 10:34:52 +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 9E94C40684 for ; Fri, 30 Sep 2022 10:34:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664526891; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HJ9FC2nMwwg4F1tn3U2W1AutD4xXfzpEgiS1Gl/Lzks=; b=RGcpE/5VA1nRHsq0DhPTEwV82nzSayjVAvdeOC5UQ0HFV5BCK3WgeyVQl+RBNY8B9K5Osz FdxDkN8qpsjBgqFdW6/F49ZF8q4AC9F2k6ruoUZVQkUikHnrypsbOMYkooH/3m5rjKPt9/ +ftwYnX+UmMyUG4YKgtBe4TJlN2tyac= Received: from mail-pf1-f199.google.com (mail-pf1-f199.google.com [209.85.210.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-448-djJSygROMDeVwOHIBoJsvw-1; Fri, 30 Sep 2022 04:34:46 -0400 X-MC-Unique: djJSygROMDeVwOHIBoJsvw-1 Received: by mail-pf1-f199.google.com with SMTP id u10-20020a056a00098a00b00543b3eb6416so2453698pfg.15 for ; Fri, 30 Sep 2022 01:34:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date; bh=HJ9FC2nMwwg4F1tn3U2W1AutD4xXfzpEgiS1Gl/Lzks=; b=xuerJ2iHrmr2kAfE7/krdFP8T0KgFry7xo1JPCsPBxT7S50ulz0ZDvViTdntZlmBEA gnFf0U7/S18PLhBahxErUzWdQjTXPQ/wTAKgHQwP+kcR8Wr33HfZlUe9qgQggAgY2jSR +pgu9NzXFqsL6guHGqgMRB17qbgAGO3ookzNakHiBuvO8Jogh5A5FCWsm86lV5WJnCfL 1zFI2WMgtoAV7kcR9XtryvskcFRZtOx4XuYHxnQM6hRmzAOPxJfAtfnYwpIVoFT+qh/m G96wT5gqPXt8FYFsKtoMMZBiaxY8akJsO2fBtyx0PBqizF9pJOAUxChydqt5Z418Dafs cMqw== X-Gm-Message-State: ACrzQf3NNzQen2efk4eptWUL1hcOs61mdZqJ3oOAdvhWkIhL5Fe4OCPS CdmU4S/lvGR/6b740YX3jgX2kiUBDgYxKynX2zr76nuvxzcVOdhv0L3Wchfa/BmrFFh3dBm33Ay jBxhiDzHEW99RgNUbGPs= X-Received: by 2002:a63:a556:0:b0:439:f022:426a with SMTP id r22-20020a63a556000000b00439f022426amr6629434pgu.120.1664526885872; Fri, 30 Sep 2022 01:34:45 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4l0mGkMazTp+/xOfQQkXNMyv3CWvRwpaD8WfYlPiyjola1Limv4Hsy54DjWLtO6WZ6tnh/C49pMCnRvqBaJt0= X-Received: by 2002:a63:a556:0:b0:439:f022:426a with SMTP id r22-20020a63a556000000b00439f022426amr6629417pgu.120.1664526885577; Fri, 30 Sep 2022 01:34:45 -0700 (PDT) MIME-Version: 1.0 References: <20220820103032.119741-1-mb@smartsharesystems.com> In-Reply-To: <20220820103032.119741-1-mb@smartsharesystems.com> From: David Marchand Date: Fri, 30 Sep 2022 10:34:34 +0200 Message-ID: Subject: Re: [PATCH] x86: rte_mov256 was missing for AVX2 To: =?UTF-8?Q?Morten_Br=C3=B8rup?= Cc: bruce.richardson@intel.com, konstantin.v.ananyev@yandex.ru, dev@dpdk.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 On Sat, Aug 20, 2022 at 12:30 PM Morten Br=C3=B8rup wrote: > > The rte_mov256 function was missing for AVX2. Afaiu: Fixes: 9144d6bcdefd ("eal/x86: optimize memcpy for SSE and AVX") This has been missing for a long time, so I guess nobody actually uses it. > > Signed-off-by: Morten Br=C3=B8rup Acked-by: Bruce Richardson Applied, thanks. If you think it is worth always including the generic/ headers in all arch specific headers, can you work on it? Thanks. --=20 David Marchand