From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw1-f44.google.com (mail-yw1-f44.google.com [209.85.161.44]) by dpdk.org (Postfix) with ESMTP id 54FDD1150 for ; Sat, 13 Oct 2018 23:05:01 +0200 (CEST) Received: by mail-yw1-f44.google.com with SMTP id v1-v6so6246617ywv.6 for ; Sat, 13 Oct 2018 14:05:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HmUmKRYQ8sDQqPqzNcsD444iALiYJPrGg1b40zTsefQ=; b=QmxpIwKzA5n6JN30+itlD7Oqv56dxtVxQ5s9ysJx0m7YXcawvdcI9YCcjT8hzknOyF GJ5VaDpXTnZOd2SNFE8usn2ugz8jxUjjwzuARUZfF+vjbtOs7n4LLGv6G+ZhlIFgOdNr k3RbcnXCXjQmKzYn4tb269hTWCKGtgFWshS2KynpqcFp8a0zDCU58q0Nq086uEcZElnc uojo9sn4FlBedj7W+eQkPRTNZrH3159RKv0/dRlgJUxHll4FCPmh2zLa287nGZgxOglj XErofDIk6JnWJHEwvURMDVJMI0ryTS9ymht+u222PQDIGYzr23EExQG7PHAF6SCvpCQ6 xX4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HmUmKRYQ8sDQqPqzNcsD444iALiYJPrGg1b40zTsefQ=; b=PYTmy8ky9ws/YYcl6+JCYUgnTL6uaPtcpchmkcKu66uIRpML/gVvXJPNWvcRMGCzsM 3HVdpKEumR9nKLgucNUZu9fWc8n3WNVPgDRJkEz/E8nO+kbXn9+DAsPu3AjybmVdYmWR Au3VSiJ/uG4lNX4f4ERknVYGmlFJOpLva63VlIsJHAEHC+mX4MTOZxsOj7RBnH7Q2c2j 3+r0Cp7arJeMLVDBNO0W9WZvDuaWHBtGNnIYOcpmowuF6gGUVIL6e3v6lTpAFbyPa+jV EGk2pXW8QTW6M0Gu2SuwmofQ6yH0cT0/7gsCmHHu9Sw0e0NzCQgmdnpw2iXK/c+RlhSo dZLg== X-Gm-Message-State: ABuFfogHMMp3DYf9KfqSA2QGNN+UgiAnaWBLk1J4bpj022VC9Ot4aJtS koeDy1BSyLABMUL3fKidWuWc7/8cgBLgyyIqcQo= X-Google-Smtp-Source: ACcGV63XO2wH0KlRlUDBII187x8gRUAAQJxMgPhCc7g+vEForSlvWGl4DbMzztur9lXYQrhDX8nY3AKce7A2sopT5SA= X-Received: by 2002:a0d:fbc2:: with SMTP id l185-v6mr3792614ywf.446.1539464700447; Sat, 13 Oct 2018 14:05:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Cliff Burdick Date: Sat, 13 Oct 2018 14:05:08 -0700 Message-ID: To: philippb.ontour@gmail.com Cc: users Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] rte_eth_tx_burst: Can I insert timing gaps 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: Sat, 13 Oct 2018 21:05:01 -0000 Maybe I'm misunderstanding the problem, but do you need to transmit anything? Can you just use the rte_cycles functions to sleep for the remaining period in 20ms? On Thu, Oct 11, 2018 at 2:04 AM Philipp B wrote: > Hi all! > > I am working on an RTP test traffic generator. The basic idea is > clock_nanosleep providing a 20ms clock cycle to start a (big) number > of rte_eth_tx_bursts, sending equally sized buffers. As long as the > timing within a 20ms cycle is dictated primarily by the line speed, I > can be sure that not just the first buffer of each cycle has a period > of 20ms, but also the n-th buffer. (I have sent n-1 buffers before > with the same size.) > > Basically, I see one 20ms interval as a series of time slots, each > capable to store an active RTP stream. My question now is, what to to > with inactive time slots? As long as all active streams are located at > consecutive time slots from the start of the 20ms interval, everything > is fine. But I cannot guarantee this. > > What I need is some kind of dummy buffer, which is not transmitted but > generates a tx timing gap as a buffer of X bytes would take to be > transferred. > > Is such a functionality provided? As a workaround, I already thought > about sending invalid packets (bad IP Header checksum?). However, this > won't be optimal when multiple lines are aggregated. > > Thanks! > Philipp Beyer >