From: Benny Halevy <bhalevy@panasas.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Weston Andros Adamson <dros@netapp.com>,
Boaz Harrosh <bharrosh@panasas.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 22:13:11 +0300 [thread overview]
Message-ID: <4DE68F47.5080802@panasas.com> (raw)
In-Reply-To: <1306951621.3873.45.camel@lade.trondhjem.org>
On 2011-06-01 21:07, Trond Myklebust wrote:
> On Wed, 2011-06-01 at 17:51 +0300, Benny Halevy wrote:
>> I think the following should work:
>>
>> Benny
>>
>> git diff --stat -p -M
>> fs/nfs/nfs4filelayout.c | 10 ++++++++++
>> 1 files changed, 10 insertions(+), 0 deletions(-)
>>
>> diff --git a/fs/nfs/nfs4filelayout.c b/fs/nfs/nfs4filelayout.c
>> index 4269088..9f1d445 100644
>> --- a/fs/nfs/nfs4filelayout.c
>> +++ b/fs/nfs/nfs4filelayout.c
>> @@ -661,6 +661,16 @@ filelayout_pg_test(struct nfs_pageio_descriptor
>> *pgio, struct nfs_page *prev,
>> u64 p_stripe, r_stripe;
>> u32 stripe_unit;
>>
>> + /*
>> + * FIXME: ideally we should be able to coalesce all requests
>> + * that are not block boundary aligned, but currently this
>> + * is problematic for the case of bsize < PAGE_CACHE_SIZE,
>> + * since nfs_flush_multi and nfs_pagein_multi assume you
>> + * can have only one struct nfs_page.
>> + */
>> + if (desc->pg_bsize < PAGE_SIZE)
>> + return 0;
>> +
>> if (!pnfs_generic_pg_test(pgio, prev, req))
>> return 0;
>
> So, there are several things that bother me about pnfs_generic_pg_test()
> too now that I'm looking more closely at it:
>
> 1. If the intention is to coalesce 'prev' and 'req', shouldn't we
> be asking for a layout with req_offset(prev) instead of
> req_offset(req)?
> 2. If we're only requesting a layout of length pg_count, don't we
> still need to test the layout length that the server actually
> returned before we can allow the coalescing?
> 3. if (!pgio->lseg), shouldn't we be returning an error of some
> sort? Right now we're returning 'true', and allowing the
> coalesce to occur.
> 4. Furthermore, shouldn't that test guarding the
> pnfs_update_layout() call rather be an 'if (pgio->pg_lseg ==
> NULL)' instead of looking at the values of pg_count and
> prev->wb_bytes?
>
or rather we get the layout for the first page in
nfs_pageio_do_add_request when desc->pg_count == 0?
Then, this lseg would be useful for nfs_flush_multi
if we failed to coalesce, or we failed to get a layout
altogether we go the nfs path and can reset pg_test to
nfs_generic_pg_test.
Otherwise I agree with your assertions above.
Benny
next prev parent reply other threads:[~2011-06-01 19:13 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
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 [this message]
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=4DE68F47.5080802@panasas.com \
--to=bhalevy@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bharrosh@panasas.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