From: Ian Campbell <icampbell@arcom.co.uk>
To: Linux MTD Mailing List <linux-mtd@lists.infradead.org>
Subject: Re: Caching of reads
Date: 21 Nov 2001 15:10:30 +0000 [thread overview]
Message-ID: <1006355430.17354.8.camel@LinuxDev> (raw)
In-Reply-To: <30843.1005925709@redhat.com>
> Strange. JFFS2 doesn't do caching - that's supposed to be handle by the
> Linux VFS/VM. But set CONFIG_JFFS2_FS_DEBUG=1 and
> echo 9 > /proc/sys/kernel/printk, then see what it's actually being asked
> to read each time.
Hi,
I've instrumented my kernel a bit and found that the reads are being
caused by calls to jffs2_follow_link (in order to resolve the sym links
for the libraries needed to load sleep)...
It's been pointed out to me that the jffs list might be a better place
so I'll take this there...
Thanks,
Ian.
--
Ian Campbell
Design Engineer
Arcom Control Systems Ltd,
Clifton Road,
Cambridge CB1 7EA
United Kingdom
Tel: +44 (0)1223 411200 ext. 3204
E-Mail: icampbell@arcom.co.uk
Web: http://www.arcomcontrols.com
_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.
This message has been checked for all viruses by MessageLabs Virus Control Centre.
Company registered in England No. 1608562.
Registered Office: Unit 8, Clifton Road, Cambridge, CB1 7EA, United Kingdom, Tel: 01223 411200.
next prev parent reply other threads:[~2001-11-21 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 15:37 Caching of reads Ian Campbell
2001-11-16 15:48 ` David Woodhouse
2001-11-21 15:10 ` Ian Campbell [this message]
2001-11-21 15:46 ` David Woodhouse
2001-11-21 16:33 ` Ian Campbell
2001-11-29 9:08 ` David Woodhouse
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=1006355430.17354.8.camel@LinuxDev \
--to=icampbell@arcom.co.uk \
--cc=linux-mtd@lists.infradead.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