From: Jens Axboe <axboe@suse.de>
To: Nicolas Pitre <nico@cam.org>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Russell King" <rmk@arm.linux.org.uk>,
"Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"Marcus Meissner" <meissner@suse.de>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Only use MSDOS-Partitions by default on X86
Date: Tue, 6 May 2003 21:20:56 +0200 [thread overview]
Message-ID: <20030506192056.GM905@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0305061509090.11648-100000@xanadu.home>
On Tue, May 06 2003, Nicolas Pitre wrote:
> On Tue, 6 May 2003, Jens Axboe wrote:
>
> > On Tue, May 06 2003, Nicolas Pitre wrote:
> > > On Tue, 6 May 2003, Jens Axboe wrote:
> > >
> > > > On Tue, May 06 2003, Alan Cox wrote:
> > > > > On Maw, 2003-05-06 at 18:23, Nicolas Pitre wrote:
> > > > > > According to Alan it's nearly possible to configure the block layer out
> > > > > > entirely, which would be a good thing to associate with a CONFIG_DISK option
> > > > > > too.
> > > > >
> > > > > David Woodhouse I believe..
> > > >
> > > > Are we talking about everything below submit_bh/bio? Shouldn't be too
> > > > hard to write a small no-block.c for that...
> > >
> > > The idea is to configure out everything not needed when only NFS and/or JFFS
> > > (which doesn't rely on the block layer to work) are used. Pretty useful for
> > > networked or embedded machines.
> >
> > I see, that would indeed be a bigger job :). Just the block layer would
> > not be hard, especially if you make the restriction that the block
> > drivers usable would be ones that used a make_request strategy for
> > handling requests. That would allow you to kill ll_rw_blk.c,
> > deadline-iosched.c, and elevator.c. That's some 21k of text and 2k of
> > data on this box.
>
> That's certainly a good start.
How easy it is depends on which drivers need to work - which? mtdblock
comes to mind, a quick glance reveals that should be a breeze to make
work. It would even simplify it a bit, as the 'push request handling to
thread context' could be killed as well.
--
Jens Axboe
next prev parent reply other threads:[~2003-05-06 19:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030505210811.GC7049@wohnheim.fh-wedel.de.suse.lists.linux.kernel>
[not found] ` <1052218090.28792.15.camel@dhcp22.swansea.linux.org.uk.suse.lists.linux.kernel>
[not found] ` <20030506120939.GB15261@wohnheim.fh-wedel.de.suse.lists.linux.kernel>
2003-05-06 12:28 ` [PATCH] Only use MSDOS-Partitions by default on X86 Marcus Meissner
2003-05-06 12:42 ` Jörn Engel
2003-05-06 14:03 ` Russell King
2003-05-06 15:32 ` Jörn Engel
2003-05-06 17:13 ` Russell King
2003-05-06 17:23 ` Nicolas Pitre
2003-05-06 17:26 ` Alan Cox
2003-05-06 18:30 ` Jens Axboe
2003-05-06 18:42 ` Nicolas Pitre
2003-05-06 18:49 ` Jens Axboe
2003-05-06 19:10 ` Nicolas Pitre
2003-05-06 19:20 ` Jens Axboe [this message]
2003-05-06 19:54 ` Jens Axboe
2003-05-06 21:01 ` David Woodhouse
2003-05-07 7:22 ` Jens Axboe
2003-05-07 7:41 ` David Woodhouse
2003-05-07 7:43 ` Jens Axboe
2003-05-06 17:42 ` [PATCH] Only use MS-DOS-Partitions " Riley Williams
2003-05-05 21:08 [PATCH] Only use MSDOS-Partitions " Jörn Engel
2003-05-06 10:48 ` Alan Cox
2003-05-06 12:09 ` Jörn Engel
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=20030506192056.GM905@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=meissner@suse.de \
--cc=nico@cam.org \
--cc=rmk@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).