From owner-freebsd-hackers@freebsd.org Mon Nov 9 19:27:15 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5FDC546B5F3 for ; Mon, 9 Nov 2020 19:27:15 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CVLbl23CPz3n1R for ; Mon, 9 Nov 2020 19:27:14 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qk1-x735.google.com with SMTP id q5so4877002qkc.12 for ; Mon, 09 Nov 2020 11:27:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=S2GmGZ518aI3dC/UuxEO/UPAny5OVFSTwrbkdGnCo1c=; b=bY5KCyQ6l5Qj/9FW9F1WizSdYDmvLlIByRkT5A9KA5PJPlpSwAUqG7QaFNW7GyCRql pwFbS9jvouCz/t3QD3xlR2ixfCfofHcfJpFxBKCFo7M4i2IMaa2uBDAnfjGnDkRnB0Ht 6oQ4vNKVG0whadWIwODycbkM/b8SaTRyCJ723b2+InRXNP3jmyB08W9yaia97gQkBYZz 18l/W3voEFf6VuVEFSN05+8eWxfNkED+eYch9T1R9FxCTt+jcUWYDLP1jg7UNezKy0/A iakCYl2clov0gK/aE4DJQdwkTZVXRo1PZXp9mo3jq+E9i+2OVFFcgla0uZwmpr65vE0g lY2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to; bh=S2GmGZ518aI3dC/UuxEO/UPAny5OVFSTwrbkdGnCo1c=; b=T0IvHY2XFHXHFZMAGG2QUwpt6KIWPKbLKB7XoTM1DPL+bfiXTeJoYpHw3f+lzxlcK1 Bc5GeZjeYiK2fyxx/4e5+kfuf05hbJqgg6j8CEa1d+MCd+kOGj1Ag65shz13v1waQrP1 nuLy8iXq1wM/aepCCSmKQtZ8GqkHeeZzA9DlEF3LdkgruvuOXBL12iYmilr0s0bGYIeW 1Qi1F2/znSdUcKybOl4iutjinpwLwkQKqfychgj833DKS/RmQh3NJNVjXS0WwjEgRAx+ pcz4SYU6HBPg/7gxI46bQYQyOfp6Ry13ss6nyI7ph77OA4lQ2LZwAGvpRe7i9i+sunez fSOw== X-Gm-Message-State: AOAM531O/BdC+Bnp3EcETCnK5LZFZyAF5o3NNijH1MGdBqxlK5nfiWEp SJFv1YBVI9RQTDFcmhq8Ddc= X-Google-Smtp-Source: ABdhPJxS1oWMOj1jcQtkVmB4yivlC+kKONHQt4SHPV1I8GgjkhqKwsLxPlOBm2hL3HNwTpnDTpHj7A== X-Received: by 2002:a05:620a:10ac:: with SMTP id h12mr10458114qkk.165.1604950034199; Mon, 09 Nov 2020 11:27:14 -0800 (PST) Received: from raichu ([142.126.164.150]) by smtp.gmail.com with ESMTPSA id v15sm2114366qto.74.2020.11.09.11.27.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Nov 2020 11:27:13 -0800 (PST) Sender: Mark Johnston Date: Mon, 9 Nov 2020 14:27:11 -0500 From: Mark Johnston To: =?iso-8859-1?Q?=D6zkan?= KIRIK Cc: "freebsd-hackers@freebsd.org" Subject: Re: QAT driver Message-ID: <20201109192711.GC4990@raichu> References: <20201026200059.GA66299@raichu> <723fbd7326df42ce30cd5e361db9c736@neelc.org> <20201027032720.GB31663@raichu> <20201027125508.GD31663@raichu> <20201109185304.GB4990@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Rspamd-Queue-Id: 4CVLbl23CPz3n1R X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2020 19:27:15 -0000 On Mon, Nov 09, 2020 at 10:08:33PM +0300, Özkan KIRIK wrote: > This is cutted output, full output is attached. It's using C620. I think > it's supported. > There are two QAT chips SoC. Is it possible to use both of them ? > > none100@pci0:181:0:0: class=0x0b4000 card=0x00008086 chip=0x37c88086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'C62x Chipset QuickAssist Technology' > class = processor > none101@pci0:182:0:0: class=0x0b4000 card=0x00008086 chip=0x37c88086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'C62x Chipset QuickAssist Technology' > class = processor Yes, this should be recognized by the driver. This particular device type is untested though, so I'd be interested in hearing results on way or another. There shouldn't be any problem using multiple qat(4) instances, though this was not tested either. In OpenCrypto's model each session is bound to a specific device and new sessions are bound to the device with fewest sessions, so if you have at least two crypto sessions active in your workload both QAT devices will be used, for better or worse. > On Mon, Nov 9, 2020 at 9:53 PM Mark Johnston wrote: > > > On Mon, Nov 09, 2020 at 09:44:40PM +0300, Özkan KIRIK wrote: > > > great job! thank you! > > > > > > Does the work supports Xeon D-2100 series ? (Exact model: Xeon D-2146NT) > > > Regards