From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id E4B0BA0563; Wed, 15 Apr 2020 21:19:41 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8DA7C1D9EC; Wed, 15 Apr 2020 21:19:41 +0200 (CEST) Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150084.outbound.protection.outlook.com [40.107.15.84]) by dpdk.org (Postfix) with ESMTP id 1BF101D9CF for ; Wed, 15 Apr 2020 21:19:40 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FeP7jdCFFBPzDYRgQaWuhbVBAdl830oUsMOJwFN0QXvVq8048k/G/kcZs5gzSH/ip9ptgYdF6yOU5J6DfijdQBB9tReVgaKcRqw/C2rIjX1O90L54NhwdgCKj3Hi0ZGBw/U9yWYWOtTg/rxVi3vFMIL4GOZNOdNXOc+uApTzfAkk2ZSWdNpZ+orV1mnxneFzfjGEKePzlw0HqJ98zVzg5s0ME8DqjqRld9KjhQ4XzFTGqBS02ypG2HPVu6YsTtvAuHZF90Rhhmvb0UeLoo3tdTncrnYOTQMEzmXV5dukhjm/wLOSZUpzzC8cU8VmZ5LlLVJUj0NylMAMSy2f2VtocA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=d0VWHEQcIfX/rQV7x9CTkfAIp45G/W2GYTV9iFuFK3I=; b=GcHOQhazSevyZ+g4dm5Y3kKzCVpRDl3loaJ1PgF01arhjyAgMTiEt9l4COAeA/JnIYDPFcjyONrWD5452AaOX0Hu66SSAMwcx1IpOANr/Bb2MT/RLSjD6I03A8IGQwYnrf1Tt1AOPGsmP97fKfyztEDA7xz5oK4x2NmlsqUXdu/vQpBax0xTNnpQBKDnw48tJFSRQpcMbdIPN1Tuj84mi5z4E4Wx5VefcJCuxem8WBczDBSte8zKxpcJJuto5LJ//X1zNWJXp+8IXSVQHKI1CuzOz9FVCF3+s0NcopvNNhgvC3vqkh7atFDxYTxXodIrK7+cF4Zt68u3432d2+Lo0Q== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nxp.com; dmarc=pass action=none header.from=nxp.com; dkim=pass header.d=nxp.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nxp.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=d0VWHEQcIfX/rQV7x9CTkfAIp45G/W2GYTV9iFuFK3I=; b=NlMXhiCnQu2f5Bci09e99M1F9Cp358SmyzDyUB5iBDueJqrDA34dcDTIHzXVqXblowrqdpfRUhvVUzWLRynW4k/uI+2tAphJMaSsz3NyqKr4xOnYOWOKpWwIR5btlxKrjiC5PkRt1cZgU+2/Mc1r0PK8xb2IxN2Ziqb+4lGmPr8= Received: from VI1PR04MB3168.eurprd04.prod.outlook.com (2603:10a6:802:6::10) by VI1PR04MB7086.eurprd04.prod.outlook.com (2603:10a6:800:121::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2921.25; Wed, 15 Apr 2020 19:19:39 +0000 Received: from VI1PR04MB3168.eurprd04.prod.outlook.com ([fe80::8c03:2f5:3b48:ba74]) by VI1PR04MB3168.eurprd04.prod.outlook.com ([fe80::8c03:2f5:3b48:ba74%7]) with mapi id 15.20.2900.028; Wed, 15 Apr 2020 19:19:39 +0000 From: Akhil Goyal To: Vladimir Medvedkin , "dev@dpdk.org" CC: "konstantin.ananyev@intel.com" Thread-Topic: [PATCH v2] examples/ipsec-secgw: remove limitation for crypto sessions Thread-Index: AQHWEmdobV3w6TSvw0WaSifC+J4kh6h6jt8g Date: Wed, 15 Apr 2020 19:19:39 +0000 Message-ID: References: <6001e9c347d26c4e2f80765c8abc7f74fcf8bbf2.1586873664.git.vladimir.medvedkin@intel.com> In-Reply-To: <6001e9c347d26c4e2f80765c8abc7f74fcf8bbf2.1586873664.git.vladimir.medvedkin@intel.com> Accept-Language: en-IN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=akhil.goyal@nxp.com; x-originating-ip: [45.118.166.69] x-ms-publictraffictype: Email x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: 5b610103-b6ab-4d33-f18d-08d7e171f147 x-ms-traffictypediagnostic: VI1PR04MB7086: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:5516; x-forefront-prvs: 0374433C81 x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR04MB3168.eurprd04.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(39860400002)(366004)(136003)(346002)(376002)(396003)(4326008)(186003)(110136005)(9686003)(55016002)(76116006)(44832011)(66476007)(66446008)(64756008)(86362001)(316002)(66946007)(52536014)(66556008)(33656002)(2906002)(81156014)(4744005)(478600001)(6506007)(71200400001)(8936002)(8676002)(5660300002)(7696005)(26005); DIR:OUT; SFP:1101; received-spf: None (protection.outlook.com: nxp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: 0r+Gg3U8nLEXLeC3q224MYr3DIhx8qhiricnmXShYS87L3LoyA1A+ar24tqUfC45COkyARcteliTPlolnD8MNdTTqmThCy+kfTzxAyW6XCw7IgrclTaxhSc/yXFW/3q5645OPP+rGPZgKJnaU55M1/ZG+AYzSrd9rWgq2Yp7qsefcIarSkAbkNV09qql3pgkHLAmmwH+bKHgDGv1wflnyQfpEMduNGxLnxLKcvSl8NZdiZ0nXgmWzc3sCCDiI0ewMZ03/LjvO9bwfLmk7/NMyDO/HcbEbhB0iBHzuJC6KrshfDHWt2MdCZCycTGNw4KtRhXPZZ9iGpIEEc1PfdJfF6FCKaE+ybvZbhOM+mqFp9CeAJ/NCLDenZeMGzSNpaCxdDpt7WwwAHiqiMZPtVxWNjBd53jcb1ooT6jI57orAg960jiC7elSUgc0psPtPIqI x-ms-exchange-antispam-messagedata: DWwG3TuRAv6zFXmXxfQndfsFfoo+qDs8sBt2Qe+dRP0Q89UvSeqhYScCubClBOd33aas95t08iWryGFuoC8fxPlg1gYEg/lfAou385qZ1ORd/M63glzmS9/KpYQjAhGobE1MUajHAPmhbsYT4XV+GA== x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: nxp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 5b610103-b6ab-4d33-f18d-08d7e171f147 X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Apr 2020 19:19:39.0863 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: fWAv8EjLQzn2wHKtZg+R4nx4kIUm5NNBw6RZux8aJwdCDitazG+Bz9jDulXFh6WiT/jgQsv/wy2JQPWIZANHew== X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR04MB7086 Subject: Re: [dpdk-dev] [PATCH v2] examples/ipsec-secgw: remove limitation for crypto sessions X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Vladimir, >=20 > Get rid of hardcoded limit of cryptodev sessions. >=20 > Fixes: e1143d7dbbf4 ("examples/ipsec-secgw: get rid of maximum SA limitat= ion") > Cc: vladimir.medvedkin@intel.com >=20 > Signed-off-by: Vladimir Medvedkin > --- This will create an issue in case of rte_security sessions. Rte_security session create APIs were not updated when the provision for ha= ving Separate mempools for session and session private data was introduced. As a result the number of entries in session_priv_pool should be double the= number of Supported sessions - one for session and one for session priv data. This should be fixed in rte_security API but this would mean an API breakag= e which cannot Be done before 20.11. So this patch need to be deferred till it is not fixe= d in rte_security. Or we can have double the number of required entries in mempool. Regards, Akhil