linux-kernel - Why will NFS client spend so much time on file open?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4ae3c140608240015v6078fc29r287601aad7a2f1dc@mail.gmail.com>
Date:	Thu, 24 Aug 2006 03:15:38 -0400
From:	"Xin Zhao" <uszhaoxin@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org
Subject: Why will NFS client spend so much time on file open?

Hi,

I did Apache benchmark and collected the performance results at the
file system call level.
The microbenchmark results were collected when I did "make" on Apache
source code.

The results are very interesting:

		      open	        read		
Total Time (s)  21.599 	         15.948 											Count		   310274 	
 98028 											Time/Call (ms)	69.61 	         162.69

The results show that NFS spent even more time on file open than on
file read. But this result confuses me: what does NFS do to open a
file? As far as I know, it just issues a lookup() RPC to get file
handle, and maybe a getattr() RPC to get file attributes. This should
not take so much time. Can someone explain why this could happen?

Thanks,
-x
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/