From: Edward Shishkin <edward.shishkin@gmail.com>
To: Daniel Horne <daniel.horne@gmail.com>
Cc: ReiserFS Development List <reiserfs-devel@vger.kernel.org>
Subject: Re: reiser4 patches and todo list
Date: Sun, 08 Jan 2012 17:13:24 +0100 [thread overview]
Message-ID: <4F09C0A4.1000109@gmail.com> (raw)
In-Reply-To: <CAJZSrNLmtNDcm=FyqwQQKdo4jQ71NBN_n=GwA=NC2saZG73bww@mail.gmail.com>
[...]
On 01/08/2012 04:43 PM, Daniel Horne wrote:
>
>
> Your patch for 2.6.39-1 seems to compile fine on 3.0, but not on
> 3.1 or
> 3.2. The problem seems to be that the patch re-adds the
> PF_FLUSHER flag
> to the sched.h, as it relies on it, but on 3.1 and on that
> flag's value
> is used for the PF_NPROC_EXCEEDED flag.
>
> I'd be tempted to to swap the PF_FLUSHER check for PF_SWAPWRITE,
> as all
> kthreads that set PF_FLUSHER also set PF_SWAPWRITE, but there'd
> be some
> false-positives there and I'm not sure what effect this would have.
>
>
> Hello Daniel,
>
> I don't see any PF_FLUSHER flag in vanilla 3.2, so it shouldn't
> be an issue.
>
> There is one more problem with 3.X. I have described it here:
> http://marc.info/?l=reiserfs-__devel&m=132603099732236&w=2
> <http://marc.info/?l=reiserfs-devel&m=132603099732236&w=2>
>
> Thanks,
> Edward.
>
>
>
> There isn't a PF_FLUSHER, but the value it used to have is now defined
> as PF_NPROC_EXCEEDED.
Ah, you are right.
> I suppose we could define PF_FLUSHER to be 0x00080000, as that doesn't
> seem to be taken.
Yes, that's the way.
We need to make sure that task is a flusher, so I think using
PF_SWAPWRITE for this purpose is not a good idea..
Thanks!
Edward.
prev parent reply other threads:[~2012-01-08 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 10:51 reiser4 patches and todo list doiggl
2012-01-05 13:53 ` Edward Shishkin
[not found] ` <CALvMQwQTTcsf0w+qneYGKfsjN5WfXCf_6uvyVeaso25nGy+OrA@mail.gmail.com>
2012-01-08 13:53 ` Edward Shishkin
[not found] ` <CALvMQwRHLD19SZqxFZrAZkih+zKdfPjVoWe-m1HhtQcdA9E4mQ@mail.gmail.com>
2012-02-08 23:22 ` Edward Shishkin
[not found] ` <CAJZSrNKytiwVW_0oVmeck=e+jw2NRimAW38OKvWu3QiKb+w5zg@mail.gmail.com>
[not found] ` <4F09B7F2.5030804@gmail.com>
[not found] ` <CAJZSrNLmtNDcm=FyqwQQKdo4jQ71NBN_n=GwA=NC2saZG73bww@mail.gmail.com>
2012-01-08 16:13 ` Edward Shishkin [this message]
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=4F09C0A4.1000109@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=daniel.horne@gmail.com \
--cc=reiserfs-devel@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 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.