From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 214FFA05D3 for ; Thu, 23 May 2019 20:49:46 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 756BA493D; Thu, 23 May 2019 20:49:45 +0200 (CEST) Received: from userp2130.oracle.com (userp2130.oracle.com [156.151.31.86]) by dpdk.org (Postfix) with ESMTP id 64AE61C0B for ; Thu, 23 May 2019 20:49:44 +0200 (CEST) Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x4NIiN5m043223 for ; Thu, 23 May 2019 18:49:43 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=to : from : subject : message-id : date : mime-version : content-type; s=corp-2018-07-02; bh=AQe557CHw88UlThSLFD6TEEMsEQvWYm5bqiJ2OJbFI8=; b=Othrog6gCD+pssd5u72fFpwQGrP9M2nDdeop32BmZLdvGn9MIsNhoVYWmwJRR2XlrvYF gr7p7CtyZDul/ZKQ4oHRMCNVqeWtWBlfOKfEEl3JekyNZ1xdE7mlirU+pExCFG1I+9V7 gJKZuAIgDjyNDmVKFPl8ivCjnmtDq5kBwCAVxIQpwvfXg8sTAeIJ02WhCTZXQqucdHQU h5RJ27aYM3FcYQoYonrH3+6XW9cpsRQgJdKFNMDDy+T7wJ6CPjrb0aK00PQRZ7B/z3s4 OIEWACDYtxtpF1zFnGryf7u8SrnV+nsG611S1kyz0GyMFSgjc5HTC+vFT6dMjncrnkfO OQ== Received: from aserp3020.oracle.com (aserp3020.oracle.com [141.146.126.70]) by userp2130.oracle.com with ESMTP id 2smsk5mdv8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 23 May 2019 18:49:43 +0000 Received: from pps.filterd (aserp3020.oracle.com [127.0.0.1]) by aserp3020.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x4NIm9Nm172278 for ; Thu, 23 May 2019 18:49:42 GMT Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserp3020.oracle.com with ESMTP id 2smsh2ecaa-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 23 May 2019 18:49:42 +0000 Received: from abhmp0022.oracle.com (abhmp0022.oracle.com [141.146.116.28]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id x4NInfAb006589 for ; Thu, 23 May 2019 18:49:42 GMT Received: from [10.138.241.174] (/10.138.241.174) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 23 May 2019 18:49:41 +0000 To: users@dpdk.org From: Meng Wang Organization: Oracle Corporation Message-ID: Date: Thu, 23 May 2019 14:49:39 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Language: en-US X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9266 signatures=668687 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=1 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905230125 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9266 signatures=668687 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905230125 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] [crypto-QAT] how does qat sym pmd setup session 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: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi, I find it a bit confusing that in qat_sym_pmd.c, session_pool was not set when sym qp was setup, as shown below. static int qat_sym_qp_setup(struct rte_cryptodev *dev, uint16_t qp_id,     const struct rte_cryptodev_qp_conf *qp_conf,     int socket_id, struct rte_mempool *session_pool __rte_unused) However, later on when qat sym builds request it explicitly looks for session info in qat_sym_build_request(), which ends up with failure. Did I miss something during device and qp setup? How does qat sym setup session info for qp? Thanks, Meng