linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Drokin <green@linuxhacker.ru>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [LSF/MM ATTEND] FS jitter testing, network caching, Lustre, cluster filesystems.
Date: Sun, 15 Jan 2017 18:38:43 -0500	[thread overview]
Message-ID: <D863EDBD-277B-4CC3-854F-D57FF4501542@linuxhacker.ru> (raw)

Hello!

   I would like to attend filesystem track in the LSF/MM this year.

   Other than the obvious Lustre related stuff (ie hearing from Christoph
   how bad Lustre is and what other parts of it we need to remove),
   I can share hopefully useful testing methods we came up with in our group
   that more people can benefit from apparently, as evidenced by some interest
   from NFS people due to a bunch of problems I was able to uncover.
   I suspect other networking filesystems would benefit here.

   I also see there's potentially going to be a caching discussion that sounds
   pretty relevant to Lustre too.
   This probably would go hand-in-hand with a somewhat recent discusison with Al Viro
   about potentially redoing "unmount the subtrees on dentry invalidation" that
   appears to be overly aggressive now.

   A container support from filesystems is also very relevant to us since Lustre
   is used more and more in such settings.

Bye,
    Oleg

             reply	other threads:[~2017-01-16  0:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-15 23:38 Oleg Drokin [this message]
2017-01-16 17:17 ` [LSF/MM ATTEND] FS jitter testing, network caching, Lustre, cluster filesystems J. Bruce Fields
2017-01-16 17:23   ` Jeffrey Altman
2017-01-16 17:42     ` Chuck Lever
2017-01-16 17:46       ` James Bottomley
2017-01-16 20:39         ` Authentication Contexts for network file systems and Containers was " Jeffrey Altman
2017-01-16 21:03           ` [Lsf-pc] " James Bottomley
2017-01-17 16:29             ` Jeffrey Altman
2017-01-17 16:34               ` Trond Myklebust
2017-01-17 17:10                 ` Jeffrey Altman
2017-01-16 17:32 ` [Lsf-pc] " James Bottomley
2017-01-16 18:02   ` Oleg Drokin
2017-01-16 18:21     ` James Bottomley
2017-01-16 18:39       ` Oleg Drokin
2017-01-16 20:58         ` James Bottomley
2017-01-17  7:00           ` Oleg Drokin
2017-01-17 14:26             ` James Bottomley
2017-01-17 17:41               ` Oleg Drokin
2017-01-17 14:56             ` James Bottomley

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=D863EDBD-277B-4CC3-854F-D57FF4501542@linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --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).