linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Drokin <green@linuxhacker.ru>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: lsf-pc@lists.linux-foundation.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	containers@lists.linux-foundation.org
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] FS jitter testing, network caching, Lustre, cluster filesystems.
Date: Mon, 16 Jan 2017 13:02:41 -0500	[thread overview]
Message-ID: <F7FABA22-8B7D-4C77-A360-4454A5571C8F@linuxhacker.ru> (raw)
In-Reply-To: <1484587952.2540.42.camel@HansenPartnership.com>


On Jan 16, 2017, at 12:32 PM, James Bottomley wrote:

> On Sun, 2017-01-15 at 18:38 -0500, Oleg Drokin wrote:
>>   A container support from filesystems is also very relevant to us 
>> since Lustre    is used more and more in such settings.
> 
> I've added the containers ML to the cc just in case.  Can you add more
> colour to this, please?  What container support for filesystems do you
> think we need beyond the user namespace in the superblock?

Namespace access is necessary, we might need it before the superblock is there
too (say during mount we might need kerberos credentials fetched to
properly authenticate this mount instance to the server).

Separately, I know that e.g. NFS tries to match underlying mounts to share
them "under the hood", so there might be a single superblock used with
several namespaces potentially, I imagine.
In Lustre it might be beneficial to do something like this too in order to conserve
resources and potentially have better fs cache sharing.
I fact the whole caching thing is somewhat complicated with memory groups too,
and if we allow shared caching between several containers, would become even more complicated.

I am sure there's a bunch of pitfalls there too that we are not realizing yet that
other people have already encountered and it would be useful to find about them.

  reply	other threads:[~2017-01-16 18:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-15 23:38 [LSF/MM ATTEND] FS jitter testing, network caching, Lustre, cluster filesystems Oleg Drokin
2017-01-16 17:17 ` 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 [this message]
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=F7FABA22-8B7D-4C77-A360-4454A5571C8F@linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=containers@lists.linux-foundation.org \
    --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).