From: "J. Bruce Fields" <bfields@fieldses.org>
To: Marc Eshel <eshel@almaden.ibm.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Linux pNFS status meeting 07/15
Date: Thu, 15 Jul 2010 13:28:36 -0400 [thread overview]
Message-ID: <20100715172836.GC15126@fieldses.org> (raw)
In-Reply-To: <20100714212928.GD8161@fieldses.org>
Notes:
Bruce:
- nothing to report (transitioning to new hardware, etc.)
Trond:
- did some fsync cleanup
- bugfixes to handling of ERR_DELAY on sequence operations.
- preparing for rpc changes required for migration.
(some discusison here of idempotency problems on
migration/reboot)
Benny:
- Included Trond's delay/sequence fix
(missed some additional discussion)
Andy:
- simplification of write_pagelist/read_pagelist prototypes
- making sure layouts removed on server reboot
- looking at layout commit/reclaim issues in preparation for
discussion at Maastricht.
- wants to rename some structures; will mail proposal to list.
Jim Rees:
- bugfixing complex-volume patches; not ready to submit to Benny
quite yet.
Steved:
- Discussion of RHEL prospects. When will we have some pnfs
patches that are ready to review? Concensus seems to be
2.6.36 will be too early. Ricardo, Benny think 2.6.37
possible to finish up remaining work, squash changes into a
single cleaned-up patch series. Trond reminds that adequate
time is required before merge window for review, especially
for large change. Benny volunteering to do squashing.
--b.
next prev parent reply other threads:[~2010-07-15 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF01D34025.9BF2DCCC-ON88257760.007510C5-88257760.007530DA@us.ibm.com>
2010-07-14 21:29 ` Linux pNFS status meeting 07/15 J. Bruce Fields
2010-07-15 17:28 ` J. Bruce Fields [this message]
2010-07-15 18:24 ` Jim Rees
2010-07-15 20:26 ` sfaibish
2010-07-17 14:58 ` [nfsv4] " 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=20100715172836.GC15126@fieldses.org \
--to=bfields@fieldses.org \
--cc=eshel@almaden.ibm.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 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.