From: Alex Tomas <alex@clusterfs.com>
To: cmm@us.ibm.com
Cc: Dmitriy Monakhov <dmonakhov@sw.ru>, linux-ext4@vger.kernel.org
Subject: Re: delayed allocatiou result in Oops
Date: Wed, 20 Jun 2007 12:15:09 +0400 [thread overview]
Message-ID: <4678E20D.6060108@clusterfs.com> (raw)
In-Reply-To: <1182270229.4113.8.camel@dyn9047017103.beaverton.ibm.com>
Mingming Cao wrote:
> Hmm, PageMappedToDisk is probably not sufficient enough for pagesize!
> =blocksize. Is that the reason we need page->private to pass the
> request?
PageMappedToDisk isn't enough in that case, definitely. bh is the way
to track state of each block (this is what i'm implementing now), but
I think current nobh version (per-page flags are used) is valuable.
> That's good to know, thanks for the update. So probably above error case
> handling will be addressed in the new version?
well, you actually can move that SetPagePrivate() few lines above
(Dmitriy already tested this).
> BTW, can you point me your latest and greatest mballoc patch? I am
> trying to forward port and merge that patch to ext4 patch queue....
I don't have version for mainline yet. will prepare soon. thanks for
your interest.
thanks, Alex
next prev parent reply other threads:[~2007-06-20 8:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 7:23 delayed allocatiou result in Oops Dmitriy Monakhov
2007-06-15 5:14 ` Alex Tomas
2007-06-15 23:16 ` Mingming Cao
2007-06-16 8:02 ` [PATCH] ext4:fix invariant checking in ext4_rebalance_reservation Dmitriy Monakhov
2007-06-18 21:09 ` Mingming Cao
2007-06-19 5:56 ` Dmitry Monakhov
2007-06-16 8:14 ` delayed allocatiou result in Oops Dmitriy Monakhov
2007-06-19 1:01 ` Mingming Cao
2007-06-19 7:11 ` Alex Tomas
2007-06-19 9:16 ` Dmitry Monakhov
2007-06-19 9:36 ` Alex Tomas
2007-06-19 21:50 ` Andreas Dilger
2007-06-19 16:23 ` Mingming Cao
2007-06-19 16:47 ` Aneesh Kumar K.V
2007-06-20 8:15 ` Alex Tomas [this message]
2007-06-20 23:46 ` Mingming Cao
2007-06-21 4:50 ` Dmitry Monakhov
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=4678E20D.6060108@clusterfs.com \
--to=alex@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=dmonakhov@sw.ru \
--cc=linux-ext4@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