From: Benny Halevy <bhalevy@tonian.com>
To: Fred Isaman <faisaman4@gmail.com>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "Isaman, Fred" <Fred.Isaman@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] pnfs: do not reset to mds if wb_offset != wb_pgbase
Date: Sun, 28 Apr 2013 18:20:45 +0300 [thread overview]
Message-ID: <517D3E4D.4010607@tonian.com> (raw)
In-Reply-To: <5152E3B5.8080402@tonian.com>
On 2013-03-27 14:19, Benny Halevy wrote:
> On 2013-03-19 22:28, Fred Isaman wrote:
>> On Tue, Mar 19, 2013 at 3:35 PM, Benny Halevy <bhalevy@tonian.com> wrote:
>>> On 2013-03-18 19:04, Fred Isaman wrote:
>>>> A problem case is if the layout ends within the page request, which
>>>> can happen due to the misalignment.
>>>
>>> First, the file layout currently supports only whole file layouts so I don't see
>>> how that's a problem.
>>> Regardless, I'd rather trim the layout segment to PAGE_SIZE boundaries
>>> and get a new layout from the page aligned offset and on with minlength = PAGE_SIZE
>>> (as we do today).
>>>
>>> Benny
>>>
>>
>> Yes, but consider....
>>
>> let P = PAGE_SIZE
>>
>> assume you have a layout from 0 to 4P, and you try to do a WRITE from
>> 2P to 6P. Now if the buffer is not page aligned, one of the nfs_page
>> requests will contain the file's logical 4P offset at a random
>> location within the nfs_page. What happens then?
>
> Fred, Can you please provide a test that reproduces this concern
> so we can verify the system behavior with and without my patch?
Ping...
>
> Benny
>
>>
>> Fred
>> --
>> 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
>>
prev parent reply other threads:[~2013-04-28 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1363617532-24172-1-git-send-email-bhalevy@tonian.com>
2013-03-18 15:55 ` [PATCH] pnfs: do not reset to mds if wb_offset != wb_pgbase Myklebust, Trond
2013-03-18 16:22 ` Benny Halevy
2013-03-18 16:39 ` Myklebust, Trond
2013-03-18 16:45 ` Benny Halevy
2013-03-18 17:09 ` Myklebust, Trond
2013-03-18 17:04 ` Fred Isaman
2013-03-19 19:35 ` Benny Halevy
2013-03-19 20:28 ` Fred Isaman
2013-03-19 20:38 ` Benny Halevy
2013-03-27 12:19 ` Benny Halevy
2013-04-28 15:20 ` Benny Halevy [this message]
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=517D3E4D.4010607@tonian.com \
--to=bhalevy@tonian.com \
--cc=Fred.Isaman@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=faisaman4@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/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).