From: Artem Bityutskiy <dedekind@infradead.org>
To: xiaochuan xu <xiaochuanxv@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: about the _dtype_ parameter
Date: Mon, 05 Jan 2009 17:14:07 +0200 [thread overview]
Message-ID: <1231168447.6608.26.camel@localhost.localdomain> (raw)
In-Reply-To: <ff5b6bcd0901050659k4679c64egffcfa054da4c9034@mail.gmail.com>
On Mon, 2009-01-05 at 22:59 +0800, xiaochuan xu wrote:
> Hi,
>
> >> In my test, I found that the third parameter of ubi_wl_get_peb()
> >> function _dtype_ is always UBI_SHORTTERM.
>
> >Which test?
> I write a temporary file in the ubifs with O_TRUNC flag over and over.
> I see that all the @dtype variables are equal to 2 not 3.
> why does this happen?
Hmm, indeed, UBIFS uses UBI_SHORTTERM in 'reserve_space()', which looks
wrong - thanks for noticing. Could you please try the attached patch?
> Even though, as you say, most of the data are type of UBI_UNKNOWN,
> the @dtype variable seems to make less sense in the current implemenation.
> If this is ture, I think it's necessary to implement a
> dynamic-data-type-classification
> policy.
Agree. I'll be happy to merge such an improvement, but I do not have
plans to do this myself.
Patch:
diff --git a/fs/ubifs/journal.c b/fs/ubifs/journal.c
index 10ae25b..6a885c5 100644
--- a/fs/ubifs/journal.c
+++ b/fs/ubifs/journal.c
@@ -208,7 +208,7 @@ again:
offs = 0;
out:
- err = ubifs_wbuf_seek_nolock(wbuf, lnum, offs, UBI_SHORTTERM);
+ err = ubifs_wbuf_seek_nolock(wbuf, lnum, offs, UBI_UNKNOWN);
if (err)
goto out_unlock;
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next parent reply other threads:[~2009-01-05 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ff5b6bcd0901050659k4679c64egffcfa054da4c9034@mail.gmail.com>
2009-01-05 15:14 ` Artem Bityutskiy [this message]
2009-01-12 9:26 ` about the _dtype_ parameter xiaochuan-xu
2009-01-13 9:41 ` Artem Bityutskiy
2009-01-14 16:37 ` xiaochuanxv
2009-01-14 17:02 ` xiaochuanxv
2009-01-14 12:48 ` Artem Bityutskiy
[not found] <TWMHGPGDBZQLPDUUCZBAWZYAUCWM.20061402067@cqu.edu.cn>
2009-01-05 13:15 ` Artem Bityutskiy
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=1231168447.6608.26.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=xiaochuanxv@gmail.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