From: andros@netapp.com
To: bhalevy@panasas.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] pnfs-submit Re-initialize pnfs_layout_type when segs list is empty
Date: Fri, 9 Jul 2010 12:39:29 -0400 [thread overview]
Message-ID: <1278693571-3328-1-git-send-email-andros@netapp.com> (raw)
e keep the nfs_inode->layout when the segs list is empty, and we remove it
from the nfs_client cl_layouts list, but we fail to reset the other fields.
Re-initialize the layout (all except for the refcount) so that the next
layoutget with potentially new deviceid.... sets the layout fields.
Note: API change to layoutdriver_io_operations free_layout
0001-SQUASHME-pnfs-submit-reinitialize-pnfs_layout_type.patch
0002-SQUASHME-pnfs-submit-file-layout-free_layout-init_on.patch
Tested
CONFIG_V4_I set:
Connectathon tests pass against GFS2/pNFS and pyNFS file layout servers. Both
return-on-close and not return-on-close tested.
CONFIG_V4_I not set:
NFSv4.0 mount passes Connectathon tests.
-->Andy
next reply other threads:[~2010-07-09 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 16:39 andros [this message]
2010-07-09 16:39 ` [PATCH 1/2] SQUASHME pnfs-submit: reinitialize pnfs_layout_type andros
2010-07-09 16:39 ` [PATCH 2/2] SQUASHME pnfs-submit file layout free_layout init_only andros
2010-07-12 16:10 ` [PATCH 1/2] SQUASHME pnfs-submit: reinitialize pnfs_layout_type Benny Halevy
2010-07-12 15:48 ` [PATCH 0/2] pnfs-submit Re-initialize pnfs_layout_type when segs list is empty Boaz Harrosh
2010-07-12 16:36 ` William A. (Andy) Adamson
[not found] ` <AANLkTinjab9XPUjRe2knYyRQg8j9pmc9Gdk_fRkGGfY2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-12 17:07 ` Boaz Harrosh
2010-07-12 18:07 ` William A. (Andy) Adamson
[not found] ` <AANLkTilSPhZ1aBtU1taI8UnKQ9CddgaK3oQ1xoSMOuh3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-13 9:02 ` Boaz Harrosh
2010-07-13 14:06 ` William A. (Andy) Adamson
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=1278693571-3328-1-git-send-email-andros@netapp.com \
--to=andros@netapp.com \
--cc=bhalevy@panasas.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).