From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 93195C31E45 for ; Thu, 13 Jun 2019 20:04:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6B5AA2133D for ; Thu, 13 Jun 2019 20:04:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="Vf0Co9J1" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729241AbfFMUEQ (ORCPT ); Thu, 13 Jun 2019 16:04:16 -0400 Received: from mail-io1-f41.google.com ([209.85.166.41]:33893 "EHLO mail-io1-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728997AbfFMUEQ (ORCPT ); Thu, 13 Jun 2019 16:04:16 -0400 Received: by mail-io1-f41.google.com with SMTP id k8so769790iot.1 for ; Thu, 13 Jun 2019 13:04:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc; bh=DI3nny5EkaaAj92ROhz8+oF1JyVO+F50iFiYFfny5cg=; b=Vf0Co9J1FWQf/mNg9X22WqwFrqk1bWNDchM2WOC0coX4mVxqvFdL4M7qSSiticNd+/ +3h8YyGJXb6Dp9fwIq4WsLEKSNJVZR/j3S/HsXXpkjb7r3yKx1VfkTt2fSEW7Upj2InB vpUy4mSkuPaOLlVxWUk8m4jGlNkrR8m+OQY9c= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc; bh=DI3nny5EkaaAj92ROhz8+oF1JyVO+F50iFiYFfny5cg=; b=HTqLoZetM9sylxXE66lczzZWoOPsk7fsjtzMM1qNqsK9CN15zaBXpg9LdDbJPmqiuG GeYSKTcLw+WAEIyVIzaIOM4AEf4miGiFiRd5eqsKPJCGP6QpIEV2/XQXX/IJF3jyJI/b 3f+a+QxLhHXPuIf1aVaKDBbc99HoJE9BfAi7V7m5l0xeEdZXVvEcxoUjPOPi5w3q3C3w Sebyu9muKk2ozzIZlu48EPs20pe6LNCWkE8L4F8PKCcz+/Mr4yRd6nDymh9tQeEgBN9U vWsS/opiovu+rerl/X2L5MCPalcNxBGW1L3ZSl4pl2mLPqrpQ6TfDPyhCW5w0duk/He2 Devg== X-Gm-Message-State: APjAAAVkMSANlGQaHRE+g/QR50uRBcnVHSpgOnhZs95sjWeiBDqjBpSk AYcBZdBuEWhstVbdaR+wPJuyufmzlSq+WUH41I1msQ== X-Google-Smtp-Source: APXvYqzt6T4yoFnlQQM4Io9z3VVKv9jXWB1wt4QkxYaqK+pkTNNNf6XRH7RjKzaoumZniM5JtnYN2SZhYMEkCQ+APaM= X-Received: by 2002:a5d:9b1a:: with SMTP id y26mr37376851ion.238.1560456255599; Thu, 13 Jun 2019 13:04:15 -0700 (PDT) From: Kashyap Desai References: <20190605190836.32354-1-hch@lst.de> <20190605190836.32354-11-hch@lst.de> <20190613084458.GB13221@lst.de> In-Reply-To: <20190613084458.GB13221@lst.de> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQNLjZIO2zMn7N+9xPobnDbFSu4o5gI2RJdJAgF+bYgCEzcr9aN60eSw Date: Fri, 14 Jun 2019 01:34:00 +0530 Message-ID: Subject: RE: [PATCH 10/13] megaraid_sas: set virt_boundary_mask in the scsi host To: Christoph Hellwig Cc: Jens Axboe , Sebastian Ott , Sagi Grimberg , Max Gurtovoy , Bart Van Assche , Ulf Hansson , Alan Stern , Oliver Neukum , linux-block@vger.kernel.org, linux-rdma@vger.kernel.org, linux-mmc@vger.kernel.org, linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org, "PDL,MEGARAIDLINUX" , PDL-MPT-FUSIONLINUX , linux-hyperv@vger.kernel.org, linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-usb-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org > > So before I respin this series, can you help with a way to figure out for > mpt3sas and megaraid if a given controller supports NVMe devices at all, so > that we don't have to set the virt boundary if not? In MegaRaid we have below enum - VENTURA_SERIES and AERO_SERIES supports NVME enum MR_ADAPTER_TYPE { MFI_SERIES = 1, THUNDERBOLT_SERIES = 2, INVADER_SERIES = 3, VENTURA_SERIES = 4, AERO_SERIES = 5, }; In mpt3sas driver we have below method - If IOC FACT reports NVME Device support in Protocol Flags, we can consider it as HBA with NVME drive support. ioc->facts.ProtocolFlags & MPI2_IOCFACTS_PROTOCOL_NVME_DEVICES Kashyap