From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <praupadhyaya@gmail.com>
Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com
 [209.85.212.175]) by dpdk.org (Postfix) with ESMTP id E8D77568F
 for <dev@dpdk.org>; Wed,  4 Mar 2015 06:23:42 +0100 (CET)
Received: by widem10 with SMTP id em10so26152044wid.0
 for <dev@dpdk.org>; Tue, 03 Mar 2015 21:23:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=r/Tz1pmpAYGAlKq8FoSuT4beZN/Lf2riNTXiY4CaLho=;
 b=BFTUKQTWyXv9PnVFt9i7oYZudNfBLSqq/XyWSzx0PA8rsA3qzA3pUK8N7JPoHkqFTN
 ek/1/XCt0vvq3jMnj9lwtMhfnEmP/sgap5h7QUZVuMwamq3ASfKuJAuBWjqqTSCZhqAI
 c4ZKCb2h8r6W2JXd4ar5wRfrgsVSMVqoOxN8meIIeRi23K577cJ3ej0q3mcVum1+9Yce
 6fl0jUyH8Wlaqg6MN8pVCiaccZGhjblwIB/Cd4GqfOWn2+rZhg2w3OqSsFEUcgbzrzyX
 RwDweSkbt8oce4xghQmLY9d50cT7JaigRAWd8PLrRg3A0m1BL52QA+YW4hc+61/uqC7M
 MFZQ==
MIME-Version: 1.0
X-Received: by 10.194.82.226 with SMTP id l2mr4236338wjy.11.1425446622753;
 Tue, 03 Mar 2015 21:23:42 -0800 (PST)
Received: by 10.194.62.74 with HTTP; Tue, 3 Mar 2015 21:23:42 -0800 (PST)
Date: Wed, 4 Mar 2015 10:53:42 +0530
Message-ID: <CAPBAu3X0ybLZGWdxQUENwk8XTxqhLsBkRSdfz5S9+pUbN7w7wA@mail.gmail.com>
From: Prashant Upadhyaya <praupadhyaya@gmail.com>
To: dev@dpdk.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] Regarding dpdk_qat example
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2015 05:23:43 -0000

Hi,

In the dpdk_qat example, the function alloc_memzone_region does the
allocation for the memory of a crypto session context. Now in a real
application, the sessions will be torn down as well. So if a similar
strategy is followed as that of alloc_memzone_region, then how can the
memory be returned to memzone. I see the comment over the
alloc_memzone_region function which indicates that the allocation is meant
to exist for a lifetime and there is no possibility to free. Or should a
real application follow a different strategy for allocating memory to
sessions, would like to know the advice of QAT users.

Regards
-Prashant