From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50]) by dpdk.org (Postfix) with ESMTP id 9EF2F282 for ; Mon, 11 Jul 2016 17:14:20 +0200 (CEST) Received: by mail-wm0-f50.google.com with SMTP id f126so94634775wma.1 for ; Mon, 11 Jul 2016 08:14:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=k6kSjM5qlKTx7T/jGst+zP0o5ertC6C7qgY5BDzhk7k=; b=aXUTHi/YCKD5sbj5+FKtAbhQMhV2MtQPjFQ7JTfxLTL9tZ/JafTpG6GFLiqr5bjZ5n MAM3zirSoNKYDX6mcPg2QtnEWXFrPfA3gTD6dxb4uPdftEyOH2FPB6YWNKzgmy41HmVM /kSJ1BGbIP5cQdBYQe2Ag+9ftv8yvt26F0I2TSmuJzyicBMTIIjGZeYOwsO7Tbrrv5Po OZPwKYA+EofEL5QRv7qZAJF7mPOVjMGCb+cJOvBYRFau2zxiWS2ZH/FIzCdNNbDqsUxN bzPKnfMtzJrB7Lvx2psD821Btbx6i+ztUgHrE19kOGEIp3GAZP2z0/FV1cJ71lBrvcWw /1cA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=k6kSjM5qlKTx7T/jGst+zP0o5ertC6C7qgY5BDzhk7k=; b=lFOedQz8Gnm9/3jFAeHFUPgz97aAbuabqvDTRJaI8wRzTS2qplTpTU/RlVBj9bAy/o +qmCUV73CZwvvRmVf3CbswMacONxnMNqviz2i66nZLSQg6Q9fXO9XI1F5cdH92xKdsZz By5zS+gGDGNG8OczQekG19w7bdZTCrC3JETOpv2+3wrV0WYlhTZuKQ5mkNZLmKpkF329 Q/0IMA9f2+JjbJTa+Cqur4tRshIctVANtOyDSFDhvnAtrM0dQVzy2QHa2+mx1RWUCw3m O4r/hWCZlcIPAj2kRtIiC+2cML/xNguvdxpCGU/TjPd48pimqw32DUQ/K9lwgIupkSc6 ZbAQ== X-Gm-Message-State: ALyK8tJq5VNCH5Tjo98S7oWMbHvwDcl4Ia8XMIxbUUfA9VfG8Aerh8ngiUBpPIbawyk5DJ5X X-Received: by 10.28.24.137 with SMTP id 131mr20885134wmy.77.1468250060411; Mon, 11 Jul 2016 08:14:20 -0700 (PDT) Received: from xps13.localnet (guy78-3-82-239-227-177.fbx.proxad.net. [82.239.227.177]) by smtp.gmail.com with ESMTPSA id h7sm300888wji.47.2016.07.11.08.14.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Jul 2016 08:14:19 -0700 (PDT) From: Thomas Monjalon To: Pablo de Lara Cc: dev@dpdk.org, declan.doherty@intel.com Date: Mon, 11 Jul 2016 17:14:15 +0200 Message-ID: <3131295.VGPtJqbz11@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <1467797930-16174-1-git-send-email-pablo.de.lara.guarch@intel.com> References: <1467797930-16174-1-git-send-email-pablo.de.lara.guarch@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] examples/l2fwd-crypto: flush crypto dev buffers X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 15:14:20 -0000 2016-07-06 10:38, Pablo de Lara: > Crypto operations are enqueued in the crypto devices > when the crypto device buffers are full (MAX_PKT_BURST), > in order to be more efficient. > > The problem is that operations might be stuck in those buffers, > if they never get full, and therefore, those operations > will never be performed. > > Therefore, it is necessary to have a buffer flush mechanism, > similar to the one used for flush the TX buffers, so eventually, > all packets received are ciphered and sent out. > > Fixes: 387259bd6c67 ("examples/l2fwd-crypto: add sample application") > > Signed-off-by: Pablo de Lara Applied, thanks