mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dean <seattleplus@gmail.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"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: Tue, 26 Jun 2012 17:03:51 -0700	[thread overview]
Message-ID: <4FEA4DE7.3030606@gmail.com> (raw)
In-Reply-To: <CAKYAXd-OT9nV--vYOseGYHp35g3qo86rzYJPDiP454ipoGJ2Xw@mail.gmail.com>

Hi Namjae,

I'm glad you also see the usefulness of sending such hints to the NFS 
server.

Beyond reviewing the  NFSv4.2 spec, it would also be very useful to 
implement a version of IO_ADVISE and show performance results with your 
traverse test (among others).  If you have time for this, that would 
really be helpful in ensuring the usefulness of IO_ADVISE.

Dean Hildebrand

On 6/24/12 6:54 PM, Namjae Jeon wrote:
> 2012/6/24, Jim Rees <rees@umich.edu>:
>> Namjae Jeon wrote:
>>
>>    > Yes, posix_fadvise support is part of NFSv4.2.
>>    Where can I check it ?
>>    Thanks.
>>
>> NFS is standardized throught the IETF.  4.2 is not out yet, so you'll find
>> it in the drafts rather than the RFCs.  You can search them here:
>> http://www.rfc-editor.org/idsearch.html
>>
>> Here is the current draft:
>> ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-nfsv4-minorversion2-12.txt
>>
> Okay, I will check, Thanks a lot Jim~. We hope to contribute 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-27  0:04 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
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 [this message]
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=4FEA4DE7.3030606@gmail.com \
    --to=seattleplus@gmail.com \
    --cc=a.sahrawat@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=linkinjeon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=namjae.jeon@samsung.com \
    --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®