Received: by 2002:ac0:b08d:0:0:0:0:0 with SMTP id l13csp4545356imc; Mon, 25 Feb 2019 06:50:30 -0800 (PST) X-Google-Smtp-Source: AHgI3Ia7tC3QpMnyRT0m71V8BwXeBGF9n1UxKZlzYeXntSmRql2WgtvUkbAMmckNuIRouhOnRstP X-Received: by 2002:a63:4247:: with SMTP id p68mr10621039pga.30.1551106230255; Mon, 25 Feb 2019 06:50:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551106230; cv=none; d=google.com; s=arc-20160816; b=EBUnkEDKVFf+AVVwunRCrWzKw3d/J9l1bZlhshk6i6iPNIg9csCw1LwrFuA7au2/Tc kMzMXPh4XnhxoHgA+Qa/3pCVuZ6NkJO2iV5a8wnQmO+A/vC/vcW7jUyPsh4VVf342Fd6 qENIq1qGxExSg6oAfOfnk0dhPDWdQh7T+hxTQAgBdHf6WytFnMt3bvRsrpDg3xxug6c0 GcYzNOhy/coKX4sjtVrkTFdnvBNiz0PNAxsv3OGfMbGkIR0e/fKGO+8z9RS0pPbSFA5F uxu3YaHoXUBVtzvqeCp0V5rij6gKLXN7AJdzg0RZiIDIjyH70IqNID6nZncfwcgXCszz mZtw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=mMDQumBGVXpA3A1u4UOXH2tePQ2H7YXxmyd0MJ93a4Q=; b=HXY66kHjgL5xgsM0uIS1qaXOoDPTJ9YDgk1vfmwQFgBxRcBVZXoTyQW1t9/CKWoPEz CjJGD8hd8vBJloCSzKWCRH0TgJ7f/UqX+i4X87O/9H6fq5GSU16RQcsjyLl1LMwtVRuh avKuCsROv++QFOmHECPWVT9yAp8YmuyE3AaZVeNKlDycCoFCRwNqFDDDyFR2FLQNQ2s9 tkiR55Qdvnmw46UWmrpgfRiboOf4pnRddPntMmps6LlvG14yzcDElCi+2j4+XjWDDZie bnfLb0ed0CW8jyB6X5Nbi0JGB/oMRHSsm/Tx6Ke6hTrDp9SAMMdq8I4+G6xjwnScA0f9 JTUA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m5si9774091plt.12.2019.02.25.06.50.14; Mon, 25 Feb 2019 06:50:30 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727549AbfBYOtI (ORCPT + 99 others); Mon, 25 Feb 2019 09:49:08 -0500 Received: from mail-pg1-f195.google.com ([209.85.215.195]:42729 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726313AbfBYOtH (ORCPT ); Mon, 25 Feb 2019 09:49:07 -0500 Received: by mail-pg1-f195.google.com with SMTP id b2so4590102pgl.9 for ; Mon, 25 Feb 2019 06:49:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=mMDQumBGVXpA3A1u4UOXH2tePQ2H7YXxmyd0MJ93a4Q=; b=FeDDEMSQxANdvGP25fOT3dUU7Vgi40O3DSA/8aelDcdJF09mV6KXCuiSxnnSfSjZmX rTSXAljc0WE6++WH6CHmXlKmSILfY7uPFwo4HsUNVwj/d8VzHQbuZfgmZffcmbECVTLe fEASjglosxLaYwAjifwt6uvl6/wkSsaTwd2MBdOL5fI0axdUGaHYp/YeFUQLgmSzC+u4 dy551Z1KrA+0Gg3NlstEd0DVtwlmelZviJkS15Qni1TtzwdDFYOCTboej/Dk6mfH7NHn HjZ3ah7jLzp96h09Q3QEMx1SqdiSu8fC3k2WUIVyQCM4g36JJy072TwptFi/d+5WW0mo go4w== X-Gm-Message-State: AHQUAub+KrJ5fxr4g8+XkpRk65rXHGk22yfSIfO+OMCKiw5bhXolutBv 4cJ3BKdH4hlIoVcbf7D6BDIHdNHb X-Received: by 2002:a63:144:: with SMTP id 65mr19648980pgb.38.1551106146952; Mon, 25 Feb 2019 06:49:06 -0800 (PST) Received: from asus.site ([2601:647:4000:5dd1:a41e:80b4:deb3:fb66]) by smtp.gmail.com with ESMTPSA id o5sm27955002pfi.118.2019.02.25.06.49.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Feb 2019 06:49:05 -0800 (PST) Subject: Re: [PATCH] nvmet: disable direct I/O when unavailable To: Johannes Thumshirn , Max Gurtovoy , Chaitanya Kulkarni , Christoph Hellwig Cc: Linux Kernel Mailinglist , Linux NVMe Mailinglist References: <20190221182234.22345-1-jthumshirn@suse.de> <6c3fa30a-d516-a453-a001-1014202ff9ce@suse.de> <9d8e96de-d68d-8961-21e8-4cb8e79b4a08@mellanox.com> <2185e4e5-086a-d0c2-0fee-a7a5c98267bb@suse.de> From: Bart Van Assche Message-ID: Date: Mon, 25 Feb 2019 06:49:04 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: <2185e4e5-086a-d0c2-0fee-a7a5c98267bb@suse.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/25/19 1:37 AM, Johannes Thumshirn wrote: > On 24/02/2019 11:54, Max Gurtovoy wrote: >> What is the status of iSCSI/SRP targets in this case ? > > iSCSI/SRP passes in the following: > > /* > * Use O_DSYNC by default instead of O_SYNC to forgo syncing > * of pure timestamp updates. > */ > flags = O_RDWR | O_CREAT | O_LARGEFILE | O_DSYNC; That code fragment comes from the LIO file backend. There is no requirement for a SCSI target core file backend to use O_DSYNC. SCST allows users to choose whether or not O_DSYNC should be used: if (virt_dev->wt_flag && !virt_dev->nv_cache) open_flags |= O_DSYNC; Bart.