From: David Howells <dhowells@redhat.com>
To: Suresh Jayaraman <sjayaraman@suse.de>
Cc: dhowells@redhat.com, trond.myklebust@netapp.com,
Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [RFC][PATCH] nfs: don't assume fscache_acquire_cookie will always succeed
Date: Sat, 23 Jan 2010 03:48:06 +0000 [thread overview]
Message-ID: <30067.1264218486@redhat.com> (raw)
In-Reply-To: <4B599FA5.5080103@suse.de>
Suresh Jayaraman <sjayaraman@suse.de> wrote:
> As I understand we should not be calling any fscache related functions when
> the client doesn't use fsc mount option (though CONFIG_NFS_FSCACHE is set),
> right?
Not necessarily. It can be done that way, but if you just set the top-level
cookie to NULL, fscache.h will just od the right thing all the way down. It
adds a test and jump to each path.
Anyway, I can't really look at it now, I'm on holiday in NZ for a couple more
weeks.
David
prev parent reply other threads:[~2010-01-23 3:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 12:21 [RFC][PATCH] nfs: don't assume fscache_acquire_cookie will always succeed Suresh Jayaraman
2010-01-20 21:35 ` Trond Myklebust
2010-01-21 11:07 ` David Howells
2010-01-21 11:41 ` Suresh Jayaraman
2010-01-22 12:52 ` Suresh Jayaraman
2010-01-23 3:48 ` David Howells [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=30067.1264218486@redhat.com \
--to=dhowells@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sjayaraman@suse.de \
--cc=trond.myklebust@netapp.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