mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Jim Rees <rees@umich.edu>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
	"bfields@fieldses.org" <bfields@fieldses.org>,
	"Trond.Myklebust@netapp.com" <Trond.Myklebust@netapp.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"bharrosh@panasas.com" <bharrosh@panasas.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Namjae Jeon <namjae.jeon@samsung.com>,
	VivekTrivedi <t.vivek@samsung.com>,
	Amit Sahrawat <a.sahrawat@samsung.com>
Subject: Re: [RFC PATCH] nfs: Support posix_fadvise(POSIX_FADV_RANDOM) on nfs server.
Date: Sat, 23 Jun 2012 09:30:36 -0400	[thread overview]
Message-ID: <5AC2C9F0-EEFE-423E-BBB9-27102D1CA163@oracle.com> (raw)
In-Reply-To: <20120623115106.GA2742@umich.edu>



Sent from my iPad

On Jun 23, 2012, at 7:51 AM, Jim Rees <rees@umich.edu> wrote:

> Namjae Jeon wrote:
> 
>  From: Namjae Jeon <namjae.jeon@samsung.com>
> 
>  This patch disable readahead for a file on NFS Server when
>  posix_fadvise(fd..., POSIX_FADV_RANDOM) is called on NFS
>  Client.
> 
> It looks like you're adding an argument to the read op.  Wouldn't that be an
> incompatible change?  In which case wouldn't it be better to propose this
> for inclusion in NFS 4.2?  In fact didn't Dean propose this?  What ever
> happened with that?

Yes, posix_fadvise support is part of NFSv4.2.

> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-06-23 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-23 10:47 Namjae Jeon
2012-06-23 11:51 ` Jim Rees
2012-06-23 13:30   ` Chuck Lever [this message]
2012-06-24  4:22     ` Namjae Jeon
2012-06-24 12:46       ` Jim Rees
2012-06-25  1:54         ` Namjae Jeon
2012-06-27  0:03           ` Dean
2012-06-27  0:39             ` Namjae Jeon
2012-06-24  4:20   ` Namjae Jeon
2012-06-23 15:09 ` Myklebust, Trond

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=5AC2C9F0-EEFE-423E-BBB9-27102D1CA163@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=a.sahrawat@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=bharrosh@panasas.com \
    --cc=linkinjeon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=namjae.jeon@samsung.com \
    --cc=rees@umich.edu \
    --cc=t.vivek@samsung.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

all inboxes | Powered by JetHome®