mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Bharath Madhavan <bharath_madhavan@ivivity.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Speeding up VFS using HW assist
Date: Wed, 23 May 2001 16:22:28 +0000	[thread overview]
Message-ID: <20010523162227.A33@toy.ucw.cz> (raw)
In-Reply-To: <25369470B6F0D41194820002B328BDD2071790@ATLOPS>
In-Reply-To: <25369470B6F0D41194820002B328BDD2071790@ATLOPS>; from bharath_madhavan@ivivity.com on Tue, May 22, 2001 at 05:11:37PM -0400

Hi!

> 	I will be using Linux as the OS for an embedded system.
> I was looking into 2.4.4 kernel code and saw the dcache implementation
> in VFS which is pretty neat and fast by itself.
> 
> My question is, will I gain any considerable efficiency in file system
> access
> if I can move this "pathname -> inode" lookup into some proprietery 
> HW assist mechanism and take out the dcache hashing and "cached_lookup"
> function.

I doubt it will do much difference. How much time is spent in kernel
in your workload? What kind of embedded system is that?

> How good(bad) was it before the dcache implementation and in which release
> was dcache feature added (was it only after 2.2.x release). 
> Did we get 2-3 times better performance with dcache? (if not, how much?)

I'd be surprised if dcache made more than 20% speedup.

> Can anyone suggest any other place in the file system (VFS and EXT2) where
> we
> can use any HW assist (let us say FPGA implementing search, lookup, etc.)
> to speed up file-system access (both for opening and read/write)

Dumping ext2 for reiserfs? ;-)


-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


      reply	other threads:[~2001-05-25  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22 21:11 Bharath Madhavan
2001-05-23 16:22 ` Pavel Machek [this message]

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=20010523162227.A33@toy.ucw.cz \
    --to=pavel@suse.cz \
    --cc=bharath_madhavan@ivivity.com \
    --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

all inboxes | Powered by JetHome®