From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rgout0807.bt.lon5.cpcloud.co.uk (rgout0807.bt.lon5.cpcloud.co.uk [65.20.0.154]) by dpdk.org (Postfix) with ESMTP id 87EFA2FDD for ; Fri, 15 Sep 2017 17:24:32 +0200 (CEST) X-OWM-Source-IP: 10.110.12.1 () X-OWM-Env-Sender: terry.montague.1980@btinternet.com X-Junkmail-Premium-Raw: score=11/50, refid=2.7.2:2017.9.15.145116:17:11.235, ip=, rules=__HAS_FROM, __FRAUD_WEBMAIL_FROM, __HAS_REPLYTO, __FRAUD_WEBMAIL_REPLYTO, __TO_MALFORMED_2, __TO_NO_NAME, __HAS_MSGID, __SANE_MSGID, INVALID_MSGID_NO_FQDN, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART, __CTYPE_MULTIPART_MIXED, __HAS_X_PRIORITY, __REPLYTO_SAMEAS_FROM_ADDY, __REPLYTO_SAMEAS_FROM_ACC, __REPLYTO_SAMEAS_FROM_DOMAIN, __MIME_TEXT_P2, __MIME_TEXT_H2, ECARD_WORD, SUPERLONG_LINE, __HAS_HTML, __HTML_TAG_DIV, HTML_NO_HTTP, BODY_SIZE_1900_1999, BODYTEXTP_SIZE_3000_LESS, BODYTEXTH_SIZE_10000_LESS, __MIME_TEXT_H1, __MIME_TEXT_P1, __MIME_HTML, BODY_SIZE_5000_LESS, __FRAUD_WEBMAIL, NO_URI_FOUND, NO_CTA_URI_FOUND, BODY_SIZE_2000_LESS, PRIORITY_NO_NAME, __MIME_TEXT_H, __MIME_TEXT_P, REPLYTO_SAMEAS_FROM, NO_URI_HTTPS, BODY_SIZE_7000_LESS Received: from webmail26.bt.ext.cpcloud.co.uk (10.110.12.1) by rgout08.bt.lon5.cpcloud.co.uk (9.0.019.13-1) (authenticated as terry.montague.1980@btinternet.com) id 58BFF08014088D61 for users@dpdk.org; Fri, 15 Sep 2017 16:24:32 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=btcpcloud; t=1505489072; bh=jIgeHUgKQYotFzDK+I+xoqAJmeheEo4eulFuZ0eTsMs=; h=Date:From:Reply-To:To:Message-ID:Subject:MIME-Version; b=qCTsEr6NyaW9rXYQB5Th3nLVP5FoYOpiFgoCSigXCmGFPw9sD7zhKfqcXUwhZnYfpgq7ddg86g5kqBjUhHGHbAeGtBn9cbGcdnPEIxja0kJqhcZoglYRELH+3wGM08aQXf2UXxsdWDfcLBTbS//I8sXKIm7oys2RaPI7oJxjh3c= Date: Fri, 15 Sep 2017 16:24:32 +0100 (BST) From: "terry.montague.1980@btinternet.com" To: users@dpdk.org Message-ID: <7969136.40614.1505489072336.JavaMail.defaultUser@defaultHost> MIME-Version: 1.0 Importance: 3 (Normal) X-Priority: 3 (Normal) X-Client-IP: IPv4[31.53.103.251] Epoch[1505489072317] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] Intel X550 Receive timestamping for all packets X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: terry.montague.1980@btinternet.com List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2017 15:24:32 -0000 Hi all, Has anyone tried modifying the ixgbe PMD driver to allow an Intel X550 card to insert the extra 8 bytes of data at the end of each receive message, the 8 bytes containing the receive SYSTIME timestamp ? I've adjusted TYPE in TSYNCRXCTL to be "all packets" and set TSIP_UT_EN. I get the 8 bytes of data appended to all packets, but the controller doesn't populate the memory - the contents are left unchanged when transmitted. TS and TSIP are both set in the received RDESC descriptor (along with the receive byte count increasing by 8 bytes) so the adaptor is definitely doing something. Any ideas anyone ? Many thanks Terry. >From rauln@cpqd.com.br Fri Sep 15 21:31:28 2017 Return-Path: Received: from mail-pf0-f179.google.com (mail-pf0-f179.google.com [209.85.192.179]) by dpdk.org (Postfix) with ESMTP id 94FD53238 for ; Fri, 15 Sep 2017 21:31:28 +0200 (CEST) Received: by mail-pf0-f179.google.com with SMTP id l188so1927326pfc.6 for ; Fri, 15 Sep 2017 12:31:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cpqd.com.br; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=xfyCKaWRrbo+fKaXr0nfUBjFFnZS5UnT+sgCXXzJZd8=; b=MHUvy8IihxrqsH0HV5T++BvIuPuC6CnwLk14zI3NprJRj99euZRhSfSH/9ueiY+C7/ MRVXoEaMOXO+/Ae2Aw2RDIgfJ55uzldzTxgW0fje/qzD/qXHxQEP7FhUaRR+Xz8Zdtn0 4ane//mOzj+1RpubJKvYX7KYspQeZZW25pAUE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=xfyCKaWRrbo+fKaXr0nfUBjFFnZS5UnT+sgCXXzJZd8=; b=m6sxFTt7NLEfEtBIGiif3ogd3Ii6eBMMnWBa5Bt0KZ+vSo6RaeNUnCJJW6l1IQQ4re 3+SzhRjrJe6a9xJqYpYoXIR5ELaP+ZzDflZ/mx2KTrO0RPAK7tpgFRh/dwaTDusLceOO Ib16K3t0BJzxIj/8Rmghu2qVT9OtXFelZaDdxYS3QvWriS9fl7ILrqm4th8dr+G/z16b 5fKouLF8NcAbGjCzZ0lNVh35O3zQOCOGNkiMh38MXunBLXBJpqzQSbp4qSq4RECfySdJ 2ghX0y6MRPYB7Y+MKIiCUXgdsWUFnkumhxBZXpNVAnnqv5Bs5OIjHC4OqcWqtTj7Fz+i lkVQ== X-Gm-Message-State: AHPjjUghvhYrkwfjLCLwkzeha98mOkW2/J3qY5dbvXEuRZaebGB2VlmX SwofXW1Vj2JZPi9ezPs6KWah0GUFbegagfBJERaGvNC5 X-Google-Smtp-Source: AOwi7QDSSuFqro23f+J9T/8+KEL9iUfH8MUS+Pnj7SZSphsdvUJRzh0RMWGqV+5NX1fnizAs1sMF5abP2Wxmn4oIl5g= X-Received: by 10.99.171.9 with SMTP id p9mr13211339pgf.30.1505503887209; Fri, 15 Sep 2017 12:31:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.179.101 with HTTP; Fri, 15 Sep 2017 12:30:56 -0700 (PDT) In-Reply-To: References: From: Raul Negreiros Date: Fri, 15 Sep 2017 16:30:56 -0300 Message-ID: To: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Help with QinQ insertion on i40e X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2017 19:31:28 -0000 Hi, I didn't notice that the default configuration in the NIC's queue is to disable TX offloading. I was using the 'rte_eth_tx_queue_setup' function with the last parameter 'tx_conf' as NULL, in this way using the default configuration. After configure the 'txq_flags' attribute properly my issue was solved and the offloading worked perfectly. Best regards, Raul Negreiros On Thu, Sep 14, 2017 at 2:15 PM, Raul Negreiros wrote: > Hi, > > I'm trying to insert QinQ in the packet using the offload feature, but > unfortunately I'm unsuccessful. > > These are my steps: > - On device configuration configuration: > - call 'rte_eth_dev_set_vlan_offload' with the following flags: > ETH_VLAN_STRIP_OFFLOAD, ETH_VLAN_EXTEND_OFFLOAD; > - call 'rte_eth_dev_set_vlan_ether_type' twice with the inner and outer > types. > - On packet processing: > - set the PKT_TX_QINQ_PKT flag on 'ol_flags' attribute; > - fill the 'vlan_tci' and 'vlan_tci_outer'. > > Did I miss something? > > Obs: My interface's driver is i40e and the DEV_TX_OFFLOAD_QINQ_INSERT flag > is > active on tx capabilities. > > Obs2: I've found on 'drivers/net/i40e/i40e_ethdev.c' the following > comment: > "Apply double-vlan setting, not implemented yet" in i40e_dev_init_vlan > function. > May it means that actually is not possible to use QinQ insertion with this > driver? > > Best regards, > > Raul Negreiros >