question about file identifier in NFS trace data

question about file identifier in NFS trace data

[Xue Peng Li]

SGksDQogICAgSSBhbSBub3cgd29ya2luZyBvbiBORlMgdHJhY2UgaG9va3Mg
b2YgTEtFVC4gSSB3YW50IHRvIGtub3cgd2hhdCBmaWxlIA0KaXMgYmVpbmcg
b3BlcmF0ZWQgZm9yIGJvdGggY2xpZW50IHNpZGUgYW5kIHNlcnZlciANCnNp
ZGUgTkZTIGZ1bmN0aW9ucy4gT24gY2xpZW50IHNpZGUsIHR3byBraW5kcyBv
ZiBkYXRhIGNhbiBiZSB1c2VkIHRvIA0KaWRlbnRpZnkgZmlsZXMsIGkuZS4g
aV9pbm8gZmllbGQgb2YgdGhlIGlub2RlIG9iamVjdA0Kd2hpY2ggY2FuIGlk
ZW50aWZ5IHRoZSBmaWxlc3lzdGVtIGlub2RlIG9uIGRpc2ssIGFuZCB0aGUg
b3RoZXIgaXMgTkZTIGZpbGUgDQpoYW5kbGVyIHdoaWNoIGlzIHVzZWQgdG8g
aWRlbnRpZnkgZmlsZXMgYmV0d2VlbiANCmNsaWVudCBhbmQgc2VydmVyLk9u
IHNlcnZlciBzaWRlICxvbmx5IE5GUyBmaWxlIGhhbmRsZXIgcmVjZWl2ZWQg
ZnJvbSANCmNsaWVudCBjYW4gYmUgdXNlZCB0byBpZGVudGlmeSBmaWxlKEl0
J3MgdmVyeSANCmNvbXBsaWNhdGVkIHRvIGNvbnZlcnQgaXQgdG8gaW5vZGUg
b2JqZWN0IGF0IG5mc2RfKiBwcm9iZSBwb2ludCkuDQogDQogICAgSSBhbSBu
b3Qgc3VyZSB3aGljaCBvbmUgc2hvdWxkIGJlIHRyYWNlZC4gSWYgZmlsZSBo
YW5kbGVyIGlzIHRyYWNlZCANCix0aGVyZSBpcyBhbm90aGVyIHByb2JsZW0g
LCB0aGUgdG90YWwgbGVuZ3RoIG9mDQpmaWxlIGhhbmRsZXIgaXMgMTI4IGJ5
dGVzLGFuZCBmb3IgTkZTVjMgdGhlIGxlbmd0aCBpcyB2YXJpYWJsZS4gSSBh
bSBub3QgDQpzdXJlIGhvdyBtYW55IGJ5dGVzIHNob3VsZCBiZSB0cmFjZWQs
IGlmIDEyOCBieXRlcw0KYXJlIHRyYWNlZCAsaXQncyB3aWxsIHNvIGxvbmcg
Zm9yIHBlcmZvcm1hbmNlIHBlbmFsdHksIHVzdWFsbHkgd2Ugb25seSANCnRy
YWNlIHNlcnZhbCBieXRlcyBmb3Igb25lIGRhdGEuDQoNCiAgIENvdWxkIGFu
eW9uZSBnaXZlIG1lIHNvbWUgc3VnZ2VzdGlvbnM/IFRoYW5rcyBpbiBhZHZh
bmNlDQoNClRoYW5rcy4NCg0KQmVzdCBSZWdhcmRzLA0KTGkgWHVlcGVuZyAg
KMDu0anF9CkNCg0KTGludXggUGVyZm9ybWFuY2UsIENoaW5hIFN5c3RlbXMg
JiBUZWNobm9sb2d5IExhYg0KQ2hpbmEgRGV2ZWxvcG1lbnQgTGFicywgQmVp
amluZw0KRW1haWw6IHh1ZXBlbmdsQGNuLmlibS5jb20NCg==

Re: [NFS] question about file identifier in NFS trace data

[Trond Myklebust]

On Tue, 2006-08-29 at 11:12 +0800, Xue Peng Li wrote:
> Hi,
>     I am now working on NFS trace hooks of LKET. I want to know what file 
> is being operated for both client side and server 
> side NFS functions. On client side, two kinds of data can be used to 
> identify files, i.e. i_ino field of the inode object
> which can identify the filesystem inode on disk, and the other is NFS file 
> handler which is used to identify files between 
> client and server.On server side ,only NFS file handler received from 
> client can be used to identify file(It's very 
> complicated to convert it to inode object at nfsd_* probe point).
>  
>     I am not sure which one should be traced. If file handler is traced 
> ,there is another problem , the total length of
> file handler is 128 bytes,and for NFSV3 the length is variable. I am not 
> sure how many bytes should be traced, if 128 bytes
> are traced ,it's will so long for performance penalty, usually we only 
> trace serval bytes for one data.
> 
>    Could anyone give me some suggestions? Thanks in advance

See what we use for dprintk(): use dentries whenever possible, else use
the combination sb->s_id + fileid.

Cheers,
  Trond

Re: question about file identifier in NFS trace data

[Xue Peng Li]

[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]

Thanks.

Best Regards,

Li Xuepeng  (李雪鹏)

Linux Performance, China Systems & Technology Lab
China Development Labs, Beijing
Email: xuepengl@cn.ibm.com

systemtap-owner@sourceware.org wrote on 2006-08-29 11:58:15:

> On Tue, 2006-08-29 at 11:12 +0800, Xue Peng Li wrote:
> > Hi,
> >     I am now working on NFS trace hooks of LKET. I want to know what 
file 
> > is being operated for both client side and server 
> > side NFS functions. On client side, two kinds of data can be used to 
> > identify files, i.e. i_ino field of the inode object
> > which can identify the filesystem inode on disk, and the other is NFS 
file 
> > handler which is used to identify files between 
> > client and server.On server side ,only NFS file handler received from 
> > client can be used to identify file(It's very 
> > complicated to convert it to inode object at nfsd_* probe point).
> > 
> >     I am not sure which one should be traced. If file handler is 
traced 
> > ,there is another problem , the total length of
> > file handler is 128 bytes,and for NFSV3 the length is variable. I am 
not 
> > sure how many bytes should be traced, if 128 bytes
> > are traced ,it's will so long for performance penalty, usually we only 

> > trace serval bytes for one data.
> > 
> >    Could anyone give me some suggestions? Thanks in advance
> 
> See what we use for dprintk(): use dentries whenever possible, else use
which filed of dentries should be traced , i_ino and file name?
> the combination sb->s_id + fileid.
do you think the combination can identify the file between server and 
client?
On server side , nfsd_proc function only receives file handler as its 
input arguments ,
how can I extract the s_id and fileid from file handler , because at 
nfsd_proc probe
point ,I can't call fh_verify to convert file handler to inode . Do you 
think it's 
possible to extract such information from file handler according to 
comments in
include/linux/nfsd/nfsfh.h
> 
> Cheers,
>   Trond
> 


[-- Attachment #2: Type: text/plain, Size: 373 bytes --]

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: [NFS] question about file identifier in NFS trace data

[Xue Peng Li]

VGhhbmtzLg0KDQpCZXN0IFJlZ2FyZHMsDQoNCkxpIFh1ZXBlbmcgICjA7tGp
xfQpDQoNCkxpbnV4IFBlcmZvcm1hbmNlLCBDaGluYSBTeXN0ZW1zICYgVGVj
aG5vbG9neSBMYWINCkNoaW5hIERldmVsb3BtZW50IExhYnMsIEJlaWppbmcN
CkVtYWlsOiB4dWVwZW5nbEBjbi5pYm0uY29tDQoNCnN5c3RlbXRhcC1vd25l
ckBzb3VyY2V3YXJlLm9yZyB3cm90ZSBvbiAyMDA2LTA4LTI5IDExOjU4OjE1
Og0KDQo+IE9uIFR1ZSwgMjAwNi0wOC0yOSBhdCAxMToxMiArMDgwMCwgWHVl
IFBlbmcgTGkgd3JvdGU6DQo+ID4gSGksDQo+ID4gICAgIEkgYW0gbm93IHdv
cmtpbmcgb24gTkZTIHRyYWNlIGhvb2tzIG9mIExLRVQuIEkgd2FudCB0byBr
bm93IHdoYXQgDQpmaWxlIA0KPiA+IGlzIGJlaW5nIG9wZXJhdGVkIGZvciBi
b3RoIGNsaWVudCBzaWRlIGFuZCBzZXJ2ZXIgDQo+ID4gc2lkZSBORlMgZnVu
Y3Rpb25zLiBPbiBjbGllbnQgc2lkZSwgdHdvIGtpbmRzIG9mIGRhdGEgY2Fu
IGJlIHVzZWQgdG8gDQo+ID4gaWRlbnRpZnkgZmlsZXMsIGkuZS4gaV9pbm8g
ZmllbGQgb2YgdGhlIGlub2RlIG9iamVjdA0KPiA+IHdoaWNoIGNhbiBpZGVu
dGlmeSB0aGUgZmlsZXN5c3RlbSBpbm9kZSBvbiBkaXNrLCBhbmQgdGhlIG90
aGVyIGlzIE5GUyANCmZpbGUgDQo+ID4gaGFuZGxlciB3aGljaCBpcyB1c2Vk
IHRvIGlkZW50aWZ5IGZpbGVzIGJldHdlZW4gDQo+ID4gY2xpZW50IGFuZCBz
ZXJ2ZXIuT24gc2VydmVyIHNpZGUgLG9ubHkgTkZTIGZpbGUgaGFuZGxlciBy
ZWNlaXZlZCBmcm9tIA0KPiA+IGNsaWVudCBjYW4gYmUgdXNlZCB0byBpZGVu
dGlmeSBmaWxlKEl0J3MgdmVyeSANCj4gPiBjb21wbGljYXRlZCB0byBjb252
ZXJ0IGl0IHRvIGlub2RlIG9iamVjdCBhdCBuZnNkXyogcHJvYmUgcG9pbnQp
Lg0KPiA+IA0KPiA+ICAgICBJIGFtIG5vdCBzdXJlIHdoaWNoIG9uZSBzaG91
bGQgYmUgdHJhY2VkLiBJZiBmaWxlIGhhbmRsZXIgaXMgDQp0cmFjZWQgDQo+
ID4gLHRoZXJlIGlzIGFub3RoZXIgcHJvYmxlbSAsIHRoZSB0b3RhbCBsZW5n
dGggb2YNCj4gPiBmaWxlIGhhbmRsZXIgaXMgMTI4IGJ5dGVzLGFuZCBmb3Ig
TkZTVjMgdGhlIGxlbmd0aCBpcyB2YXJpYWJsZS4gSSBhbSANCm5vdCANCj4g
PiBzdXJlIGhvdyBtYW55IGJ5dGVzIHNob3VsZCBiZSB0cmFjZWQsIGlmIDEy
OCBieXRlcw0KPiA+IGFyZSB0cmFjZWQgLGl0J3Mgd2lsbCBzbyBsb25nIGZv
ciBwZXJmb3JtYW5jZSBwZW5hbHR5LCB1c3VhbGx5IHdlIG9ubHkgDQoNCj4g
PiB0cmFjZSBzZXJ2YWwgYnl0ZXMgZm9yIG9uZSBkYXRhLg0KPiA+IA0KPiA+
ICAgIENvdWxkIGFueW9uZSBnaXZlIG1lIHNvbWUgc3VnZ2VzdGlvbnM/IFRo
YW5rcyBpbiBhZHZhbmNlDQo+IA0KPiBTZWUgd2hhdCB3ZSB1c2UgZm9yIGRw
cmludGsoKTogdXNlIGRlbnRyaWVzIHdoZW5ldmVyIHBvc3NpYmxlLCBlbHNl
IHVzZQ0Kd2hpY2ggZmlsZWQgb2YgZGVudHJpZXMgc2hvdWxkIGJlIHRyYWNl
ZCAsIGlfaW5vIGFuZCBmaWxlIG5hbWU/DQo+IHRoZSBjb21iaW5hdGlvbiBz
Yi0+c19pZCArIGZpbGVpZC4NCmRvIHlvdSB0aGluayB0aGUgY29tYmluYXRp
b24gY2FuIGlkZW50aWZ5IHRoZSBmaWxlIGJldHdlZW4gc2VydmVyIGFuZCAN
CmNsaWVudD8NCk9uIHNlcnZlciBzaWRlICwgbmZzZF9wcm9jIGZ1bmN0aW9u
IG9ubHkgcmVjZWl2ZXMgZmlsZSBoYW5kbGVyIGFzIGl0cyANCmlucHV0IGFy
Z3VtZW50cyAsDQpob3cgY2FuIEkgZXh0cmFjdCB0aGUgc19pZCBhbmQgZmls
ZWlkIGZyb20gZmlsZSBoYW5kbGVyICwgYmVjYXVzZSBhdCANCm5mc2RfcHJv
YyBwcm9iZQ0KcG9pbnQgLEkgY2FuJ3QgY2FsbCBmaF92ZXJpZnkgdG8gY29u
dmVydCBmaWxlIGhhbmRsZXIgdG8gaW5vZGUgLiBEbyB5b3UgDQp0aGluayBp
dCdzIA0KcG9zc2libGUgdG8gZXh0cmFjdCBzdWNoIGluZm9ybWF0aW9uIGZy
b20gZmlsZSBoYW5kbGVyIGFjY29yZGluZyB0byANCmNvbW1lbnRzIGluDQpp
bmNsdWRlL2xpbnV4L25mc2QvbmZzZmguaA0KPiANCj4gQ2hlZXJzLA0KPiAg
IFRyb25kDQo+IA0KDQo=