> MargueriteSu;2425823 Wrote:
>> I’ve done this: ‘[opensuse-kernel] btrfs high IO waiting’
> I don’t how to update mailing list, cause I seldom use it.
You just reply to a message. (Use the reply-list or reply-all feature of
your mail client). I’m not sure why you hadn’t had any replies to your
message; perhaps because you posted it yesterday evening, European time,
after everybody had left work. I just posted a reply and hopefully
somebody will now notice the issue.
> I compile kernel-3.2-rc7 using Our Global Moderator jdmcdaniel3’s
> ‘S.G.T.B’ (http://tinyurl.com/3pn8anr) and ‘S.A.K.C’
> While I replace fs/btrfs with fs/btrfs from Btrfs filesystem’s core
> developer Mason’s git repository.
> It works amazing! he added a btrfs-delay-m process, it increases
> average cpu i/o in the first seconds, maybe that process is used for
> better schedule or something, but it sucessfully concentrate cpu power
> on important things you’re doing instead of flooding cpu with all at
> and more amazing thing is that cpu usage is nearly zero when free
That’s very good news. I suggest adding that to your bug report and the
kernel list. Those are the places the developers look at, not here.
> I’ll continuously test it. And I’m working on applying SuSE’s patch
> sets to this kind of kernel I created. these patches are all for 3.1
> series. so I have to regenerate them all. it’ll take some time. but I
> hope before Feb I can supply such a self repository for others using
> btrfs like me. Then you can update from repository. the Nvidia card
> driver will be also provided to co-exist with this kernel.
> I hope SuSE could quickly push an update 3.2-rc7 with all its patches
> applied. then everyone using btrfs can use dkms method mentioned by
> mason on btrfs wiki to keep their btrfs kernel parts up to date. because
> after 3.1, there’s a Security.h patch applies globally, so that dkms
> will surely fail if you compile the most recent btrfs against it.
The current Kernel:HEAD already appears to be 3.2-rc7, so I suggest that
the best strategy is to get the kernel developers to update the btrfs or
to fork off of the KOTD. I don’t think there’s a lot of point in a
3.2 may become the kernel for opensuse 12.2. But opensuse won’t change
the kernel for 12.1, except by issuing bugfix patches. If its possible
to fix btrfs by patching the current kernel, they may do that. Best to
talk to them on the mailing list.
> Anyway I’ll keep updating this post to tell you my work. maybe this is
> the final answer finally.