public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Adam Schrotenboer <ajschrotenboer@lycosmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: patch: loop-5
Date: Wed, 21 Feb 2001 02:33:12 +0100	[thread overview]
Message-ID: <20010221023312.J1447@suse.de> (raw)
In-Reply-To: <3A931A3C.8050000@lycosmail.com>
In-Reply-To: <3A931A3C.8050000@lycosmail.com>; from ajschrotenboer@lycosmail.com on Tue, Feb 20, 2001 at 08:30:36PM -0500

On Tue, Feb 20 2001, Adam Schrotenboer wrote:
> Jens,
> 
> Please excuse this possibly stupid q. I don't know as much about kernel 
> hacking as I would like to.
> 
> I noticed that you are rewriting the loop block device to be a block 
> remapper (yes, I had noticed this before, the q just never occurred to 
> me before); does this imply that the native block size of the loop file 
> fs must be the same size as the underlying fs? exemplia gratia, ext2 fs 
> w/ block size 1024, iso image block size 2048; or ext2 block size 1024, 
> reiserfs image block size 512 (I'm assuming this is possible, but don't 
> know for sure. of course on reiserfs the likely best size is 4096 to 
> match page size, since tails are packed anyway); or perhaps a more 
> useful/common example than the previous: iso block size 2048, ext2 block 
> size 1024 (most common block size, right??).

A remapper was the original idea, and the loop-remap-XX patches did
that. But it gave me so many head aches exactly due to for example
block size differences, and also the stacking then becomes even
more problematic.

So no, the current loop patches do not use simple buffer_head
remapping.

-- 
Jens Axboe


  reply	other threads:[~2001-02-21  1:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-21  1:30 patch: loop-5 Adam Schrotenboer
2001-02-21  1:33 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-20 20:35 Jens Axboe

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=20010221023312.J1447@suse.de \
    --to=axboe@suse.de \
    --cc=ajschrotenboer@lycosmail.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