public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tibor Kendl <kendl@flexys.hu>
To: linux-kernel@vger.kernel.org
Subject: A question about disk-cacheing
Date: Mon, 24 May 2004 17:15:47 +0200	[thread overview]
Message-ID: <40B211A3.3010904@flexys.hu> (raw)

Dear list members in linux-kernel!

I had the following experiences with linux network file system clients. 
Under Intel P4 machine, Linux Debain Sarge distribution and Linux-2.6.5 
kernel i tried to use a Novell Server shrared volumes, and i used the 
ncpfs package for this purpose. This ncpfs package works very good, i 
can read/write Novell's shared directories from my linux host, in a 
10-12 user intra network with 2-4 MB/sec. I have a database application 
which stores it's data in files, instead of an SQL or any type of 
database servers. When i store that files in a Novell file server, that 
application is very slow. I set up an another linux box with a Samba 
file server, and tested that with the same data files and in this case 
it run 6-8 times faster than with Novell/ncpfs client. I've spied the 
communication between client/server with network performance monitors, 
and it had been found out that the  ncpfs client have 6-8 times bigger 
network traffic than the smbfs client. It seems to me that smbfs caches  
the files and this makes it's network traffic much less than on the 
other case. The mount option sync and async had no effect on ncpmount. 
My question is:
Who is responsible for file caching? The linux kernel, the kernel 
filesystem drivers, or something else? Does file caching works different 
on a local ext2,reiser and on a network nfs,smbfs,ncpfs file system?

Yours Faithfully!
Tibor Kendl



                 reply	other threads:[~2004-05-24 14:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40B211A3.3010904@flexys.hu \
    --to=kendl@flexys.hu \
    --cc=linux-kernel@vger.kernel.org \
    /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