All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@cambridge.redhat.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Andrew Morton <akpm@digeo.com>,
	David Howells <dhowells@redhat.com>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] do_generic_file_read / readahead adjustments
Date: Wed, 16 Oct 2002 18:55:45 +0100	[thread overview]
Message-ID: <30901.1034790945@warthog.cambridge.redhat.com> (raw)
In-Reply-To: Message from Rik van Riel <riel@conectiva.com.br>  of "Wed, 16 Oct 2002 14:36:14 -0200." <Pine.LNX.4.44L.0210161435470.1648-100000@duckman.distro.conectiva>


> On Wed, 16 Oct 2002, Andrew Morton wrote:
> > David Howells wrote:
> > >
> > > The attached patch does the following three things:
> >
> > Seems sensible.  Is there something out there which actually uses this?
> 
> I think David has a few things up his sleeve.  The patch looks
> sensible.

I'm writing a general cache for filesystems such as AFS, NFSv4, and
Lustre. Block devices are made available to the "cache manager" by means of a
filesystem that can be mounted. I'm storing meta data in an inode in the
cache, but to scan this at the moment I need to gain a "struct file" to use
with do_generic_file_read().

This involves either creating a dummy dentry and struct file (which will cause
Al Viro to come looking for me with a shotgun), or to use an extra auxilliary
filesystem mounted with do_kern_mount(), neither of which are particularly
appealing.

This patch is the alternative: make a function (do_generic_mapping_read())
that I can pass an inode or an address_space to, and make
do_generic_file_read() call that. This allows me to make use of readahead
semantics without having to reinvent them for myself.

David

  reply	other threads:[~2002-10-16 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 15:29 [PATCH] do_generic_file_read / readahead adjustments David Howells
2002-10-16 16:19 ` Andrew Morton
2002-10-16 16:36   ` Rik van Riel
2002-10-16 17:55     ` David Howells [this message]
2002-10-16 18:03       ` Andrew Morton
2002-10-16 18:08         ` David Howells
  -- strict thread matches above, loose matches on Subject: below --
2002-10-16 18:06 dhowells

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=30901.1034790945@warthog.cambridge.redhat.com \
    --to=dhowells@cambridge.redhat.com \
    --cc=akpm@digeo.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=trond.myklebust@fys.uio.no \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.