From: Steve French <smfrench@gmail.com>
To: "lsf-pc@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] Network File System and Server topics of interest
Date: Tue, 17 Jan 2017 00:57:13 -0600 [thread overview]
Message-ID: <CAH2r5mu4jFAxt7B6kEFfSkbqHG2FVH08cVJ6bYVA+4CQzQp4Rg@mail.gmail.com> (raw)
In-Reply-To: <CAH2r5muA5hsSGmP3nT75HUqpWDuN5K1o36vEfOp=6MqHbDupYw@mail.gmail.com>
I forgot to note reflink (copy offload) in the list below because it
was already called out in one of the earlier notes, but should have
included it in the list since it is particularly important in nfs and
smb3/Samba.
On Tue, Jan 17, 2017 at 12:54 AM, Steve French <smfrench@gmail.com> wrote:
> I would like to propose a discussion on various general (local and
> network) file system topics of particular interest to network file
> systems and servers
>
> - xstat (I realize that this was mentioned in an earlier thread
> - cache manager (as noted by David Howells earlier), and various
> caching features of use for SMB3/Samba and NFS
> - richacl
> - snapshot handling (making snapshots visible over a network file system)
>
> I also would like to encourage/continue the discussion of xfstest (and
> in particular how to generalize it better for network file systems
> where it can be awkward to run the largest appropriate subset of
> tests)
>
> --
> Thanks,
>
> Steve
--
Thanks,
Steve
prev parent reply other threads:[~2017-01-17 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 6:54 [LSF/MM TOPIC] Network File System and Server topics of interest Steve French
2017-01-17 6:57 ` Steve French [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=CAH2r5mu4jFAxt7B6kEFfSkbqHG2FVH08cVJ6bYVA+4CQzQp4Rg@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).