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 E0228A32A2 for ; Thu, 24 Oct 2019 18:12:08 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 6DD281EB4B; Thu, 24 Oct 2019 18:12:08 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id B06BE1EB36 for ; Thu, 24 Oct 2019 18:12:06 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Oct 2019 09:12:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.68,225,1569308400"; d="scan'208,217";a="197161644" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga008.fm.intel.com with ESMTP; 24 Oct 2019 09:12:05 -0700 Received: from fmsmsx155.amr.corp.intel.com (10.18.116.71) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.439.0; Thu, 24 Oct 2019 09:12:05 -0700 Received: from fmsmsx108.amr.corp.intel.com ([169.254.9.101]) by FMSMSX155.amr.corp.intel.com ([169.254.5.15]) with mapi id 14.03.0439.000; Thu, 24 Oct 2019 09:12:05 -0700 From: "Pathak, Pravin" To: "users@dpdk.org" Thread-Topic: QAT PMD in multi-process mode Thread-Index: AdWKhUF4DlpnJhXiQRaHlCSV9gsEKg== Date: Thu, 24 Oct 2019 16:12:05 +0000 Message-ID: <168A68C163D584429EF02A476D52744268BDF6B3@FMSMSX108.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNWEwMWY4NmUtMWY4Yy00OTJhLTk0NjItMDgzYmZkMzE3Nzg4IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiNG45blorMTNqZXpYVG5TNFE0Z2VWRjRIMWtIM0piWENXQ01TTUQwQmc1MEpTeVYrNUg2bXdyMW1QZldwb1FqMSJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-originating-ip: [10.1.200.106] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] QAT PMD in multi-process mode 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 - In multi-process model, if same QAT VF is shared between two processes whic= h are spawned from separate executables, primary process give segfault whi= le accessing QAT functions. It looks like PMD installs access functions in shared area so when secondar= y process changes those function pointers, they are no longer valid in prim= ary process. Is QAT PMD going to modified to support this mode in future? Regards Pravin