From: "J. Bruce Fields" <bfields@fieldses.org>
To: sfaibish <sfaibish@emc.com>
Cc: Marc Eshel <eshel@almaden.ibm.com>, linux-nfs@vger.kernel.org
Subject: Re: Linux pNFS status meeting 07/08
Date: Thu, 8 Jul 2010 13:45:58 -0400 [thread overview]
Message-ID: <20100708174558.GE19375@fieldses.org> (raw)
In-Reply-To: <20100708160637.GC19375@fieldses.org>
Also I'd like to hand off running and taking notes on this meeting to
someone else for a while. (Benny, maybe?) Or we can go back to making
the meeting more informal if that's preferred.
--b.
1. upstream status/merge plans (trond, bfields)
- upstream at 2.6.35-rc4.
- server side: some bugfixes merged to callback code; allocation
failures changed to return DELAY.
- discussion of error return on client callback-parsing error.
- trond: everything from before bakeathon is in nfs-2.6.36
branch or upstream. Also some file locking bugfixes
(bugzilla.kernel.org #14501). Also sending release_lockowner
more often to keep server resources down.
2. State of pNFS tree (bhalevy)
- working on patches from boaz and andy for release branch.
Anyone else have big pending patchsets?
- Jim is getting complex-volume block patches tested,
will send them out soon.
- Fred has some pending stuff ("minor cleanup")
- next week would like to start cleaning up and squashing
together patches. Also will truncate some of the history.
3. Client
3.1. Client pNFS status
- Andy needs to look at state reclaim stuff?
- Andy still wondering what to do with the nfs inode
layout pointer. What's the lifetime of the thing that
points to?
3.2. Client state management design documentation (trond)
- Also, on docs: Andy will check that wiki docs are
uptodate. And will do some more documentation of
refcnts, as will Fred.
4. Server
4.1. Todo's for minimal 4.1 server (bfields)
- still working on callback changes. Trond notes
ongoing rpc code improvements may allow us to do much
of this by keeping a single client and modifying its
transports, in which case I may be able to replace my
callbacks with single rpc tasks.
- also fixing 4.0/4.1 bug that prevents exclusive locks
on upgraded open.
4.2. pnfs
- pnfs/gfs2
- I'll ask Eric for a report on gfs2 bakeathon
testing.
- exofs
- I'll ask Brian about citi exofs setup status.
5. boston bakeathon
- October 4-8.
- Details are finalized, to be posted soon.
- If your company will be bringing large equipment, let Sorin
know.
- If anyone would be interested in sponsoring a reception or
other addition to the bakeathon, contact Sorin. (Or if you
know who at your company would handle such a thing, let Sorin
know.)
6. new business
- Sorin asked Trond for summary of layout-commit discussion.
Discussion ensued.
7. next meeting
- next week as usual.
next prev parent reply other threads:[~2010-07-08 17:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF60B406A7.E52268C8-ON8825775A.000C6BD9-8825775A.000C8A46@us.ibm.com>
2010-07-08 15:48 ` Linux pNFS status meeting 07/08 J. Bruce Fields
2010-07-08 15:54 ` sfaibish
[not found] ` <op.vfi7ssfcunckof-sXut7+96orlxdPWQvOaHCoI83tS8F2Zb0E9HWUfgJXw@public.gmane.org>
2010-07-08 16:06 ` J. Bruce Fields
2010-07-08 17:45 ` J. Bruce Fields [this message]
2010-07-09 2:36 ` sfaibish
[not found] ` <op.vfj1i5vyunckof-sXut7+96orlxdPWQvOaHCoI83tS8F2Zb0E9HWUfgJXw@public.gmane.org>
2010-07-09 3:09 ` [nfsv4] " Trond Myklebust
[not found] ` <1278644957.3148.5.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-07-09 11:31 ` Sorin Faibish
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=20100708174558.GE19375@fieldses.org \
--to=bfields@fieldses.org \
--cc=eshel@almaden.ibm.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sfaibish@emc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.