public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ion Badulescu <ionut@badula.org>
Cc: "Vivek Goyal" <vivek.goyal@wipro.com>,
	<indou.takao@jp.fujitsu.com>, <ezk@cs.sunysb.edu>,
	<viro@math.psu.edu>, <davem@redhat.com>,
	<nfs@lists.sourceforge.net>, <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] Disabling Symbolic Link Content Caching in NFS Client
Date: Mon, 2 Jun 2003 23:48:18 +0200	[thread overview]
Message-ID: <16091.50722.851659.821544@charged.uio.no> (raw)
In-Reply-To: <200306022037.h52KbNVh012849@buggy.badula.org>

>>>>> " " == Ion Badulescu <ionut@badula.org> writes:

    >> 1. Make nfs_symlink_caching dynamically tunable using /proc and
    >> sysctl interface.

     > No. Do it on a per-mount basis, like the other OS's do.

As I said to Vivek in a private mail, it would be very nice to see
if this could be done by replacing hlfsd with namespace groups.

Al Viro has already done all the VFS layer work, which should be ready
and working in existing 2.4.20 and 2.5.x kernels. What is missing is
userland support for doing a CLONE_NEWNS, and then mounting the user's
home directory, mailspool,.... in the appropriate locations at login
time.

Cheers,
  Trond

  reply	other threads:[~2003-06-02 21:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 11:09 Disabling Symbolic Link Content Caching in NFS Client Vivek Goyal
2003-06-02 20:37 ` [NFS] " Ion Badulescu
2003-06-02 21:48   ` Trond Myklebust [this message]
2003-06-02 21:56   ` Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2003-06-03 13:20 Vivek Goyal
2003-06-03 16:05 ` Trond Myklebust
2003-06-03 13:33 Edward Hibbert
2003-06-03 14:46 ` Frank van Maarseveen
2003-06-03 16:08 ` Trond Myklebust

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=16091.50722.851659.821544@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=davem@redhat.com \
    --cc=ezk@cs.sunysb.edu \
    --cc=indou.takao@jp.fujitsu.com \
    --cc=ionut@badula.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=viro@math.psu.edu \
    --cc=vivek.goyal@wipro.com \
    /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