From: Andrew Morton <akpm@osdl.org>
To: jack@suse.cz, mason@suse.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Fix ext2 error reporting on fsync
Date: Fri, 20 Jan 2006 13:33:20 -0800 [thread overview]
Message-ID: <20060120133320.71bb0997.akpm@osdl.org> (raw)
In-Reply-To: <20060120133100.500718e5.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
>
> Andrew Morton <akpm@osdl.org> wrote:
> >
> > Another approach would be to allocate a new buffer_head which "belongs" to
> > the address_space. So instead of doing:
> >
> > bh<->bh<->address_space<->bh<->bh
> >
> > we do:
> >
> > address_space
> > ^
> > |
> > v
> > bh<->bh<->bh'<->bh<->bh
> >
> > and set a magic bit in bh' which says "this is not a real bh; your
> > address_space is at *b_private".
>
> And if we do that, we can actually shrink the address_space by 2*sizeof(long):
>
3*sizeof(long)!
> - private_list can become `struct buffer_head *metadata_buffers'
>
> - and if we're going to abandon the address_space.private* genericity, we
> can remove address_space.assoc_mapping and use a new
> address_space->metadata_buffers->b_bdev->metadata_lock.
- nuke address_space.assoc_mapping, too.
Of course the cost is that written-to address_spaces will have an
associated extra bh.
next prev parent reply other threads:[~2006-01-20 21:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 17:43 [PATCH] Fix ext2 error reporting on fsync Jan Kara
2006-01-12 4:24 ` Andrew Morton
2006-01-12 10:20 ` Jan Kara
2006-01-12 11:52 ` Andrew Morton
2006-01-12 13:58 ` Chris Mason
2006-01-12 14:21 ` Jan Kara
2006-01-12 15:36 ` Chris Mason
2006-01-12 16:32 ` Jan Kara
2006-01-12 14:26 ` Jan Kara
2006-01-12 20:47 ` Andrew Morton
2006-01-13 2:08 ` Chris Mason
2006-01-13 2:16 ` Andrew Morton
2006-01-18 22:46 ` Jan Kara
2006-01-18 23:06 ` Andrew Morton
2006-01-19 12:21 ` Jan Kara
2006-01-19 21:16 ` Andrew Morton
2006-01-20 13:41 ` Jan Kara
2006-01-20 21:24 ` Andrew Morton
2006-01-20 21:31 ` Andrew Morton
2006-01-20 21:33 ` Andrew Morton [this message]
2006-01-22 22:55 ` Jan Kara
2006-01-23 0:06 ` Andrew Morton
2006-01-22 22:32 ` Jan Kara
2006-01-22 23:31 ` Jan Kara
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=20060120133320.71bb0997.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mason@suse.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;
as well as URLs for NNTP newsgroup(s).