All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [bfields: [LSF/MM TOPIC] fileservers' filesystem wishlist]
Date: Mon, 12 Mar 2012 11:17:07 -0400	[thread overview]
Message-ID: <20120312151707.GD4752@fieldses.org> (raw)

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).

--b.

(Resent to correct cc: list, sorry!)

WARNING: multiple messages have this Message-ID (diff)
From: "J. Bruce Fields" <bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
To: lsf-pc-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Cc: linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [bfields: [LSF/MM TOPIC] fileservers' filesystem wishlist]
Date: Mon, 12 Mar 2012 11:17:07 -0400	[thread overview]
Message-ID: <20120312151707.GD4752@fieldses.org> (raw)

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).

--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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2012-03-12 15:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 15:17 J. Bruce Fields [this message]
2012-03-12 15:17 ` [bfields: [LSF/MM TOPIC] fileservers' filesystem wishlist] J. Bruce Fields
2012-03-12 19:36 ` Boaz Harrosh

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=20120312151707.GD4752@fieldses.org \
    --to=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 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.