Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5891120ybi; Wed, 12 Jun 2019 10:11:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqz0E5BnvL5rARw+wvM44Sm8kpPeZGgSxukSYivmJDRi/Ti9oCtTo1WsTlWXTbujI6v9/gXs X-Received: by 2002:a17:90a:23a4:: with SMTP id g33mr208238pje.115.1560359495650; Wed, 12 Jun 2019 10:11:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560359495; cv=none; d=google.com; s=arc-20160816; b=WMHzPXtKop9IqblHpZ+VRz09KMe4YRS2iByHYPO955RB/LrB1wtMpH7HZPYeTF8M2S tXWKyd051uPgwrUEwxCtgSIHaFFJbGzB+/DliydC0y/W+XeaFociUS8kSBQIW4rS+iJR M9sXh+KjKqJkSkY9gSScZFh8zTFIEtHq+17GRAa30TKniTHmP81QYSwXjh/tF99Kk6Ux iHfwLBFz7rhVMK3BAmH3tvF4yW1kGrKhRwXISXRB5mpc91AgHL6UrHuyEQW+G60Nwe/3 feKyecF59U6wrmLKcyLHTKr1rqvTTV5gshEXphWVA18Iqhf5KGpyScbatot419EckwLw E/KA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=cJ20ZOOhLTpp1aSXQaiW9BQJ82hXo4jHUoGV6Y4pBqg=; b=jVlxvVjKHUn7UUKVUnsFU9ClclCVXK7anb/JyY4Tc64Ay+0o1gu6/rsaEDjphh6EPu wjxLwZ/nyOtorCC8iWEL8Z51a9e20HazZnN1huN3uVbYg6YcB/COzQ79rbD2Y01tKwo0 HcTinhIV7tNKZrIgiC9cxqvhhGUJ1V7L52W+4mfzU+kgaPoG7uRJSxHuz9HWJU6mSpBt YdIYFhRWZlHD+Y0Fd078md7oysoNga3lku+Sw96/BlZoIUqtvH1XUxNtZn+2U1IEC6Aq Km1D0DCBYgn+yY8fpGA14dtcnca5row6HRx7kOARQUda6y1e0BpkWJitWXhMfcMDiFVH 6epA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m127si316404pgm.231.2019.06.12.10.11.11; Wed, 12 Jun 2019 10:11:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-nfs-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-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2406289AbfFLMHk (ORCPT + 99 others); Wed, 12 Jun 2019 08:07:40 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41278 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2405914AbfFLMHj (ORCPT ); Wed, 12 Jun 2019 08:07:39 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 98F9530872C3; Wed, 12 Jun 2019 12:07:39 +0000 (UTC) Received: from [10.10.66.66] (ovpn-66-66.rdu2.redhat.com [10.10.66.66]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 46F9D5D961; Wed, 12 Jun 2019 12:07:39 +0000 (UTC) From: "Benjamin Coddington" To: "Jianchao Wang" Cc: linux-nfs@vger.kernel.org Subject: Re: Can we setup pNFS with multiple DSs ? Date: Wed, 12 Jun 2019 08:07:38 -0400 Message-ID: <28D4997E-0B02-4979-9DE3-7E87A7FD7BA1@redhat.com> In-Reply-To: <71d00ed4-78b8-cefb-4245-99f3e53e5d2a@gmail.com> References: <71d00ed4-78b8-cefb-4245-99f3e53e5d2a@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.47]); Wed, 12 Jun 2019 12:07:39 +0000 (UTC) Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org Hi Jianchao, On 12 Jun 2019, at 3:55, Jianchao Wang wrote: > Hi > > I'm trying to setup a pNFS experiment environment. > And this is what I have got, > VM-0 (DS) running a iscsi target > VM-1 (MS) initiator, mount a XFS on the device, and export it by > NFS with pnfs option > VM-2 (Client) initiator, but not mount, running a blkmapd > mount the shared directory of VM-1 by NFS > > And it semes to work well as the mountstatus > LAYOUTGET: 14 14 0 3472 2744 1 1381 1384 > GETDEVICEINFO: 1 1 0 196 148 0 5 5 > LAYOUTCOMMIT: 8 8 0 2352 1368 0 1256 1257 > > The kernel version I use is 4.18.19. > > And would anyone please help to clarify following questions ? > 1. Can I involve multiple DSs here ? Yep, you can add a new iSCSI DS with another filesystem and keep the same MD. The pNFS SCSI layout has support for multi-device layouts, but I don't think anyone has put them through the paces. The sweet spot for pNFS SCSI is large-scale FC where the fabric allows nodes different paths through different controllers. I expect the do-it-yourself with iSCSI target on linux to have a bit more limited performance benefits. > 2. Is this stable enough to use in production ? How about earlier > version, for example 4.14 ? Test it! It would be great to have more users. It would also be great to hear about your workload and if this shows any improvements. Last note - with SCSI layouts, there's no need to run blkmapd. The kernel should have all the info it needs to find the correct SCSI devices. Ben