From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH] pnfs support servers with multiple layout types
Date: Thu, 3 Mar 2016 14:50:40 +0100 (CET) [thread overview]
Message-ID: <1286720010.2387716.1457013040842.JavaMail.zimbra@desy.de> (raw)
In-Reply-To: <20160302163746.GA25527@infradead.org>
----- Original Message -----
> From: "Christoph Hellwig" <hch@infradead.org>
> To: "Tigran Mkrtchyan" <tigran.mkrtchyan@desy.de>
> Cc: "Trond Myklebust" <trond.myklebust@primarydata.com>, linux-nfs@vger.kernel.org
> Sent: Wednesday, March 2, 2016 5:37:46 PM
> Subject: Re: [PATCH] pnfs support servers with multiple layout types
>> + for(i = 0; i < num && i < NFS_MAX_LAYOUT_TYPES; i++)
>> + layouttype[i] = be32_to_cpup(p++);
>
> Can we use a bitmap and do something like
>
> layouttype |= (1 << be32_to_cpup(p++));
>
Sorry, took me a bit longer to understand what you actually was saying.
But still won't work, as we will loose the order of supported layouts.
To make it working, we can add a mount option for preferred layout:
mount -o preferred_layout=nfs4_file,vers=4.1 ....
Then client will try preferred first, and if it's not provided,
then will go through the bitmask and pick first working.
Shall I do that? Trond, any comments?
Tigran.
> that's what I did for my unsubmitted patches to submit multiple
> layouttypes in the Linux server..
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-03-03 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 12:08 [PATCH] pnfs support servers with multiple layout types Tigran Mkrtchyan
2016-03-02 12:47 ` kbuild test robot
2016-03-02 13:57 ` Tigran Mkrtchyan
2016-03-02 16:37 ` Christoph Hellwig
2016-03-02 19:22 ` Mkrtchyan, Tigran
2016-03-03 13:50 ` Mkrtchyan, Tigran [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-22 13:45 Tigran Mkrtchyan
2015-09-22 22:31 ` Trond Myklebust
2015-09-23 6:38 ` Mkrtchyan, Tigran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1286720010.2387716.1457013040842.JavaMail.zimbra@desy.de \
--to=tigran.mkrtchyan@desy.de \
--cc=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).