From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: pf-sources Kernel
Date: Mon, 23 May 2011 07:54:30 +0300 [thread overview]
Message-ID: <ircp9v$rvm$1@dough.gmane.org> (raw)
In-Reply-To: <loom.20110522T163252-238@post.gmane.org>
On 05/22/2011 05:36 PM, James wrote:
> Howdy!
>
> Anyone running pf-sources?
>
> AMD64?
>
> Arm (Pandaboard{})?
>
> Your insights and experiences are most welcome,
> including your opinion of BFS...
>
> [1] http://ck.kolivas.org/patches/bfs/bfs-faq.txt
I don't run pf-sources, but I run a BFS-patched gentoo-sources. One of
the reasons I use it is because of its support for the SCHED_ISO process
priority, which is important for audio applications. Otherwise, I would
need to use a realtime-linux kernel, which is total overkill and I don't
want to reboot into a different kernel just for an audio session. Also,
SCHED_ISO works for normal users so I don't have to launch stuff like
jack-audio as root.
Another reason I use it is because my system becomes a bit more
responsive with BFS (meaning the GUI - I use KDE). You can do that with
the mainline scheduler too, but it's not automatic; you have to set up
the cgroups feature (creating different cgroups for different
applications), and I never bothered. It's up to the distro to provide a
cgroups setup, but I don't know whether Gentoo or any other distro
actually does it. My guess is not. Without a setup, users have to
launch their applications from the terminal, which is kind of stupid.
Launching them from the GUI will place them all in the same cgroup.
So BFS it is for me :-)
next prev parent reply other threads:[~2011-05-23 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 14:36 [gentoo-user] pf-sources Kernel James
2011-05-23 4:54 ` Nikos Chantziaras [this message]
2011-05-23 17:18 ` [gentoo-user] " James
-- strict thread matches above, loose matches on Subject: below --
2011-05-25 12:12 [gentoo-user] " Alex Schuster
2011-05-25 13:15 ` [gentoo-user] " Nikos Chantziaras
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='ircp9v$rvm$1@dough.gmane.org' \
--to=realnc@arcor.de \
--cc=gentoo-user@lists.gentoo.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