| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: more on NFS performance |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Tue, 6 Mar 2001 18:28:42 +0100 |
| Cc: | Robin Humble <rjh@xxxxxxxxxxxxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <200103061700.f26H0fA30616@jen.americas.sgi.com>; from lord@sgi.com on Tue, Mar 06, 2001 at 11:00:41AM -0600 |
| References: | <lord@sgi.com> <200103061700.f26H0fA30616@jen.americas.sgi.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Tue, Mar 06, 2001 at 11:00:41AM -0600, Steve Lord wrote: > > Hi, > > Is anyone on the list NFS savvy? I need a way from the filp or dentry of > telling that a write came from the NFS server, and I cannot really look > at the ops field in the dentry, since NFS built as a module will mess this up. > > I was hoping for some flag or something which I can use to test for this > from within xfs, currently I am doing a strcmp on the task name - which is > not something I want to do really. There isn't a clean way currently AFAIK, but I guess a flag (O_MORE?) could be set in nfsd_open() in the filp. I guess it would be something similar to MSG_MORE to turn off the early truncation? If you do that, don't you need a timer to do the truncation later? -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: more on NFS performance, Steve Lord |
|---|---|
| Next by Date: | XFS problems, Stewart Samuels |
| Previous by Thread: | Re: more on NFS performance, Steve Lord |
| Next by Thread: | Re: more on NFS performance, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |