From: Boaz Harrosh <bharrosh@panasas.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: <lsf-pc@lists.linux-foundation.org>, <linux-nfs@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>
Subject: Re: [bfields: [LSF/MM TOPIC] fileservers' filesystem wishlist]
Date: Mon, 12 Mar 2012 12:36:52 -0700 [thread overview]
Message-ID: <4F5E5054.3000304@panasas.com> (raw)
In-Reply-To: <20120312151707.GD4752@fieldses.org>
On 03/12/2012 08:17 AM, J. Bruce Fields wrote:
> Apologies, this is late for a topic proposal--and I'm not really certain
> whether it merits a separate "topic" or whether it's really just an
> add-on to Ric's "linux servers as a storage server - what's missing?".
>
> In any case, I'd love to have a slot to run through a file servers'
> filesystem wishlist; probably a slide or two each for features such as:
>
> - change attributes
> - delegations/opLocks
> - share locks
> - deleted-file recovery/server-side sillyrename
> - lock recovery
>
> with a brief summary of each (and of current status in cases where we
> have a partial solution already).
>
> Plus a little time to discuss each feature, depending on interest.
>
> My main interest is knfsd, but I'd also like to look at what we could do
> for userspace (SMB and NFS) servers.
>
> I recall doing something like this (five years ago?) at the first LSF,
> and it was quite helpful (though some of the same problems remain).
>
All these topics are very important for me too
Thanks
Boaz
> --b.
>
> (Resent to correct cc: list, sorry!)
> --
> 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:[~2012-03-12 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 15:17 [bfields: [LSF/MM TOPIC] fileservers' filesystem wishlist] J. Bruce Fields
2012-03-12 19:36 ` Boaz Harrosh [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=4F5E5054.3000304@panasas.com \
--to=bharrosh@panasas.com \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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