public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Jari Ruusu <jari.ruusu@pp.inet.fi>, Jens Axboe <axboe@suse.de>,
	Rik van Riel <riel@conectiva.com.br>,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] loop.c oopses
Date: Tue, 16 Jul 2002 14:36:07 -0700	[thread overview]
Message-ID: <3D3491C7.99B35813@zip.com.au> (raw)
In-Reply-To: 20020716211455.GE1096@holomorphy.com

William Lee Irwin III wrote:
> 
> On Tue, Jul 16, 2002 at 10:42:52PM +0300, Jari Ruusu wrote:
> > The patch below fixes that remap issue, plus uncounted number of other loop
> > issues. For example, device backed loops use pre-allocated pages for zero VM
> > pressure.
> 
> I'd like to understand this (and possibly even use it) as I tend to use
> the loopback block driver often. Any chance you could break this up into
> a blow-by-blow series of bugfixes? As it is here, it's a bit much for me
> to digest as a newbie to bio.
> 
> My needs for explanation are perhaps greater than others on the cc: list,
> so it's really optional, but I'd be much obliged if you could do so.
> 

Seconded, please.  It's obviously an important patch but it's
rather large and opaque.  A description of what it is doing and
in particularly *why* it is doing it would really help.

A nice way of providing such a description is inside

/*
 * these thingies
 */

so the information is not lost.

I particular:

- Does the file_operations-based file-backed IO work with all
  crypto setups?

- What are those preallocated pages doing?  Are they really needed
  with the 2.5 VM?  What problem are they solving?

Thanks.

(BTW: check out the ARRAY_SIZE macro ;))

-

  reply	other threads:[~2002-07-16 21:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16  6:24 [BUG] loop.c oopses William Lee Irwin III
2002-07-16  7:07 ` Andrew Morton
2002-07-16  8:31   ` Jens Axboe
2002-07-16  8:52     ` Andrew Morton
2002-07-16  8:48       ` Jens Axboe
2002-07-16  9:09         ` Andrew Morton
2002-07-16  8:52       ` William Lee Irwin III
2002-07-16  9:19         ` Andrew Morton
2002-07-16  9:16           ` William Lee Irwin III
2002-07-16  9:21           ` Jens Axboe
2002-07-16 12:49       ` Rik van Riel
2002-07-16 16:36         ` Jens Axboe
2002-07-16 16:49           ` Rik van Riel
2002-07-16 17:09             ` Jens Axboe
2002-07-16 19:42               ` Jari Ruusu
2002-07-16 21:14                 ` William Lee Irwin III
2002-07-16 21:36                   ` Andrew Morton [this message]
2002-07-17  5:40                 ` Jens Axboe
2002-07-17 15:31                   ` Jari Ruusu
2002-07-20 17:03                     ` William Lee Irwin III

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=3D3491C7.99B35813@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=axboe@suse.de \
    --cc=jari.ruusu@pp.inet.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=wli@holomorphy.com \
    /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