All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jens Axboe <axboe@suse.de>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does
Date: Sun, 03 Feb 2002 11:37:59 +0000	[thread overview]
Message-ID: <11994.1012736279@redhat.com> (raw)
In-Reply-To: <20020202135749.B4934@suse.de>
In-Reply-To: <20020202135749.B4934@suse.de>  <20020131.145904.41634460.davem@redhat.com> <E16WQYs-0003Ux-00@the-village.bc.nu> <20020131232119.GN10772@conectiva.com.br> <200202021232.g12CWat01313@Port.imtp.ilyichevsk.odessa.ua>


axboe@suse.de said:
>  You can do even more than this -- I dunno what I/O interface these
> embedded system generally uses (the mtd stuff?). Provided you provide
> a direct make_request_fn entry into these instead of using the queue,
> you can basically cut all of ll_rw_blk.c and elevator.c. 

We don't even do that - look at jffs2_read_super(). The only reason it even 
_looks_ like we're using a block device is because it was the easiest way 
to arrange mounting. We only allow you to mount the 'mtdblock' device, 
which isn't actually used - all we do is use the minor number to look up 
the real underlying MTD device. The dependency on _any_ of the block code 
isn't real - I can fix it as soon as there's an incentive to do so (like 
CONFIG_BLK_DEV).

> ll_rw_block, submit_bh, and generic_make_request would be all that is left. 

Those can go too. Likewise page->buffers.

>  That should reclaim quite a lot of space. If there's any interest in
> this (has it already been done?), I can help out getting it done.

I had a go once. Long enough ago that it's probably not worth trying to find
it again. I'd suggest a boolean like CONFIG_BUFFER_CACHE which does the
really intrusive stuff like removing page->buffers, and CONFIG_BLK_DEV which
can be modular (if CONFIG_BUFFER_CACHE is on), and which controls
compilation of everything in drivers/block/ and fs/block_dev.c

--
dwmw2



  parent reply	other threads:[~2002-02-03 11:38 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-31 20:27 crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does not Petr Vandrovec
2002-01-31 20:31 ` Jeff Garzik
2002-01-31 22:53   ` [PATCH] " Petr Vandrovec
2002-01-31 22:59     ` David S. Miller
2002-01-31 23:08       ` Jeff Garzik
2002-01-31 23:43         ` David Lang
2002-01-31 23:24       ` [PATCH] Re: crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does Alan Cox
2002-01-31 23:21         ` Arnaldo Carvalho de Melo
2002-02-02 16:32           ` Denis Vlasenko
2002-02-02 12:57             ` Jens Axboe
2002-02-02 13:16               ` arjan
2002-02-02 13:52                 ` Jens Axboe
2002-02-03 11:37             ` David Woodhouse [this message]
2002-01-31 23:43         ` Jeff Garzik
2002-01-31 23:45         ` David S. Miller
2002-02-01  0:32           ` Alan Cox
2002-02-01 10:07           ` Horst von Brand
2002-02-01 10:28             ` Keith Owens
2002-02-01 11:03               ` David S. Miller
2002-02-01 11:25                 ` Keith Owens
2002-02-01 14:56                   ` Jeff Garzik
2002-02-01  8:14         ` David Woodhouse
2002-02-02  2:12         ` Chris Wedgwood
2002-02-02  3:01           ` Andrew Morton
2002-02-02  7:30             ` Chris Wedgwood
2002-02-02  7:42               ` Daniel Jacobowitz
2002-02-02  8:08                 ` Jeff Garzik
2002-02-02 19:20                   ` Daniel Jacobowitz
2002-02-02  8:06               ` Jeff Garzik
2002-02-02  8:08               ` Keith Owens
2002-02-02  8:40                 ` David Woodhouse
2002-02-02  8:59                   ` Keith Owens
2002-02-02  9:14                     ` David Woodhouse
2002-02-03  4:14         ` Eric W. Biederman
2002-02-03  7:01           ` Ralf Baechle
2002-02-03  9:13             ` Chris Wedgwood
2002-02-03 12:16             ` David Woodhouse
2002-02-03 12:33               ` Chris Wedgwood
2002-02-03 12:47               ` David Woodhouse
2002-02-03 13:40             ` Alan Cox
     [not found] <20020131.162549.74750188.davem@redhat.com>
2002-02-01  0:42 ` Alan Cox
2002-02-01  0:30   ` David S. Miller
2002-02-01  3:46     ` Jeff Garzik
2002-02-01  4:25       ` David S. Miller
2002-02-01  4:48         ` Jeff Garzik
2002-02-01  5:59           ` David S. Miller
2002-02-01  5:10         ` Keith Owens
2002-02-01  5:12           ` Jeff Garzik
2002-02-01  5:18             ` Keith Owens
2002-02-01 13:42               ` Horst von Brand
2002-02-03 23:34                 ` Keith Owens
2002-02-04 20:14                   ` Horst von Brand
2002-02-01  6:01           ` David S. Miller
2002-02-01  6:11             ` Keith Owens
2002-02-01  6:26               ` David S. Miller
2002-02-01  6:43                 ` Keith Owens
2002-02-01 15:03                 ` Alan Cox
2002-02-01 14:55                   ` Jeff Garzik
2002-02-01 15:12                     ` Petr Vandrovec
2002-02-01 16:08                     ` David Woodhouse
2002-02-04 13:24                     ` Horst von Brand
2002-02-05  7:51                       ` Jeff Garzik
2002-02-01  4:18     ` H. Peter Anvin
2002-02-01  4:35       ` Jeff Garzik
2002-02-01 15:19     ` Alan Cox
2002-02-01 19:37     ` Rob Landley
2002-02-01 19:50       ` Jeff Garzik

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=11994.1012736279@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=acme@conectiva.com.br \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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.