linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Benny Halevy <bhalevy@panasas.com>,
	Zhang Jingwang
	<zhangjingwang-U4AKAne5IzAR5TUyvShJeg@public.gmane.org>,
	linux-nfs@vger.kernel.org, iisaman@netapp.com
Subject: Re: [PATCH] pnfsblock: Lookup list entry of layouts and tags in reverse order
Date: Mon, 17 May 2010 10:53:11 -0400	[thread overview]
Message-ID: <20100517145311.GJ30737@fieldses.org> (raw)
In-Reply-To: <4BF151A7.1070003@panasas.com>

On Mon, May 17, 2010 at 05:24:39PM +0300, Boaz Harrosh wrote:
> On 05/17/2010 04:53 PM, J. Bruce Fields wrote:
> > On Wed, May 12, 2010 at 04:28:12PM -0400, bfields wrote:
> >> On Wed, May 12, 2010 at 09:46:43AM +0300, Benny Halevy wrote:
> >>> On May. 10, 2010, 6:36 +0300, Zhang Jingwang <zhangjingwang-U4AKAne5IzAR5TUyvShJeg@public.gmane.org> wrote:
> >>>> Optimize for sequencial write. Layout infos and tags are organized by
> >>>> file offset. When appending data to a file whole list will be examined,
> >>>> which introduce notable performance decrease.
> >>>
> >>> Looks good to me.
> >>>
> >>> Fred, can you please double check?
> >>
> >> I don't know if Fred's still up for reviewing block stuff?
> >>
> >> I've been trying to keep up with at least some minimal testing, but not
> >> as well as I'd like.
> >>
> >> The one thing I've noticed is that the connectathon general test has
> >> started failing right at the start with an IO error.  The last good
> >> version I tested was b5c09c21, which was based on 33-rc6.  The earliest
> >> bad version I tested was 419312ada, based on 34-rc2.  A quick look at
> >> network traces from the two traces didn't turn up anything obvious.  I
> >> haven't had the chance yet to look closer.
> > 
> > As of the latest (6666f47d), in my tests the client is falling back on
> > IO to the MDS and doing no block IO at all.  b5c09c21 still works, so
> > the problem isn't due to a change in the server I'm testing against.  I
> > haven't investigated any more closely.
> > 
> 
> You might be hitting the .commit bug, no? Still no fix. I'm using a work
> around for objects. I'm not sure how it affects blocks. I think you should
> see that the very first IO goes through layout driver then the IO is redone
> through MDS, for each node. Even though write/read returned success because
> commit returns NOT_ATTEMPTED. But I might be totally off.

I don't believe it's even attempting a GETLAYOUT.

I'll take a look at the network....--b.

  reply	other threads:[~2010-05-17 14:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10  3:36 [PATCH] pnfsblock: Lookup list entry of layouts and tags in reverse order Zhang Jingwang
     [not found] ` <20100510033610.GA5443-nK6E9TRyOkVSq9BJjBFyUp/QNRX+jHPU@public.gmane.org>
2010-05-12  6:46   ` Benny Halevy
2010-05-12 20:28     ` J. Bruce Fields
2010-05-17 13:53       ` J. Bruce Fields
2010-05-17 14:24         ` Boaz Harrosh
2010-05-17 14:53           ` J. Bruce Fields [this message]
2010-05-17 16:53             ` J. Bruce Fields
2010-05-17 17:22               ` Zhang Jingwang
     [not found]                 ` <AANLkTilUpAHrtHH8pauvYrAuD3rWgj7aDmrTOzrmU-h5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-18 16:20                   ` J. Bruce Fields
2010-05-19  4:56                     ` Tao Guo
     [not found]                       ` <AANLkTik9L15tqpSboBpb9cSTy3hVPLEK487w94pEbLrS-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-19 16:36                         ` J. Bruce Fields
2010-05-19 21:38                           ` J. Bruce Fields
2010-05-20  5:44                             ` Tao Guo
2010-05-21 23:00                               ` J. Bruce Fields

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=20100517145311.GJ30737@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bhalevy@panasas.com \
    --cc=bharrosh@panasas.com \
    --cc=iisaman@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=zhangjingwang-U4AKAne5IzAR5TUyvShJeg@public.gmane.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).