From: Benny Halevy <bhalevy@panasas.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
linux-nfs@vger.kernel.org, "Rees, James" <rees@umich.edu>
Subject: Re: [PATCH 2/3] NFS: Cleanup of the nfs_pageio code in preparation for a pnfs bugfix
Date: Thu, 09 Jun 2011 14:58:18 -0400 [thread overview]
Message-ID: <4DF117CA.50508@panasas.com> (raw)
In-Reply-To: <1307643195.25848.10.camel@lade.trondhjem.org>
On 2011-06-09 14:13, Trond Myklebust wrote:
> On Thu, 2011-06-09 at 10:51 -0700, Boaz Harrosh wrote:
>
>> 1. We will then need to go through the ld in .pg_init
>
> No. I'll fix nfs_pageio_init_read() and friends by replacing
> pnfs_get_read_ops() by something more appropriate.
>
OK, I just push the pnfs-block stuff out so you can see what I did
over your previous version so I'll rebase over the new version once
you send it.
>> 2. What happens in the none pnfs-IO error case pg_bsize will need to be
>> saved and restored to MDS value.
>
> Yes, but if you are falling back to read/write-through-mds, then you
> need to re-run the coalescing _anyway_, since the total length of the
> request needs to fit in an rsize/wsize sized request.
>
Right. So we will need a place holder to keep a separate value for
minimum OSD's pg_bsize vs. the MDS's (like what we used to have for DS's
[rw]size in the past)
Benny
>> 3. At least in objects there is no such constant limit, it all depends on
>> the layout, start and end. I thought the all point of .pg_test was
>> exactly for avoiding a constant pg_bsize. (This is what we had before)
>> 4. All "the tests make no sense..." should be moved to the no-pnfs case
>> please point these you found out, we'll need to fix them.
>>
>> Please understand that for none-files layouts pg_bsize is when IO goes
>> through MDS only.
>
> As I said, I don't see how fallback to MDS can work correctly today for
> the objects case for arbitrary values of rsize/wsize.
>
> Cheers
> Trond
next prev parent reply other threads:[~2011-06-09 18:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 22:32 [PATCH 1/3] NFSv4.1: Fix some issues with pnfs_generic_pg_test Trond Myklebust
2011-06-06 22:32 ` [PATCH 2/3] NFS: Cleanup of the nfs_pageio code in preparation for a pnfs bugfix Trond Myklebust
2011-06-06 22:32 ` [PATCH 3/3] NFSv4.1: Add an initialisation callback for pNFS Trond Myklebust
2011-06-08 0:28 ` [PATCH 2/3] NFS: Cleanup of the nfs_pageio code in preparation for a pnfs bugfix Benny Halevy
2011-06-08 0:51 ` Trond Myklebust
2011-06-08 2:30 ` Benny Halevy
2011-06-09 16:37 ` Trond Myklebust
2011-06-09 17:51 ` Boaz Harrosh
2011-06-09 18:13 ` Trond Myklebust
2011-06-09 18:58 ` Benny Halevy [this message]
2011-06-09 21:31 ` Boaz Harrosh
2011-06-08 0:53 ` [PATCH 1/3] NFSv4.1: Fix some issues with pnfs_generic_pg_test Benny Halevy
2011-06-08 1:12 ` Trond Myklebust
2011-06-08 2:24 ` Benny Halevy
2011-06-09 16:31 ` Trond Myklebust
2011-06-09 18:43 ` Benny Halevy
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=4DF117CA.50508@panasas.com \
--to=bhalevy@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bharrosh@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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