From: Boaz Harrosh <bharrosh@panasas.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Weston Andros Adamson <dros@netapp.com>,
trond@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFS: filelayout should use nfs_generic_pg_test
Date: Wed, 01 Jun 2011 16:36:41 +0300 [thread overview]
Message-ID: <4DE64069.7080103@panasas.com> (raw)
In-Reply-To: <1306930452.25992.61.camel@lade.trondhjem.org>
On 06/01/2011 03:14 PM, Trond Myklebust wrote:
> On Wed, 2011-06-01 at 08:47 +0300, Boaz Harrosh wrote:
>> On 06/01/2011 06:18 AM, Weston Andros Adamson wrote:
>>
>> pnfs_generic_pg_test is the one that gets the layout.
>>
>> What you've done is revert to MDS IO
>
> The "files" layout type always gets the layout in the pg_doio() method
> instead of the pg_test().
>
Well I don't see where? I fought this all day, when trying to make the
new code run with objlayout, which was missing the implementation of pg_test().
And never got a pnfs-IO.
I've searched the full tree for calls to pnfs_update_layout() the only
one I can see are in:
nfs_pagein_multi() - which means within a single page, right?
nfs_pagein_one() - But is protected with list_is_singular() so only in the
single page case
nfs_flush_multi() - Same as nfs_pagein_multi
nfs_flush_one() - Also here protected with list_is_singular()
and the all mighty
pnfs_generic_pg_test()
I cannot see where the filelayout is different then other layouts
in that respect. Sorry to be slow, I would like to understand?
And also be careful with nfs_generic_pg_test() it inspects
desc->bsize which is negotiated with MDS, it's very small.
> Cheers
> Trond
>
Thanks
Boaz
next prev parent reply other threads:[~2011-06-01 13:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 3:18 [PATCH] NFS: filelayout should use nfs_generic_pg_test Weston Andros Adamson
2011-06-01 5:47 ` Boaz Harrosh
2011-06-01 12:14 ` Trond Myklebust
2011-06-01 13:36 ` Boaz Harrosh [this message]
2011-06-01 13:43 ` Benny Halevy
2011-06-01 14:32 ` Benny Halevy
2011-06-01 14:44 ` Weston Andros Adamson
2011-06-01 14:51 ` Benny Halevy
2011-06-01 15:36 ` Weston Andros Adamson
2011-06-01 16:01 ` Fred Isaman
2011-06-01 18:56 ` Benny Halevy
2011-06-01 19:17 ` Trond Myklebust
2011-06-01 19:29 ` Boaz Harrosh
2011-06-01 19:38 ` Trond Myklebust
2011-06-01 19:49 ` Boaz Harrosh
2011-06-01 19:52 ` Trond Myklebust
2011-06-01 18:07 ` Trond Myklebust
2011-06-01 19:13 ` Benny Halevy
2011-06-01 19:29 ` Trond Myklebust
2011-06-01 20:09 ` Benny Halevy
2011-06-06 16:47 ` William A. (Andy) Adamson
2011-06-06 18:21 ` Benny Halevy
2011-06-06 18:22 ` Myklebust, Trond
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=4DE64069.7080103@panasas.com \
--to=bharrosh@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=dros@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond@netapp.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