From: Gilberto Nunes <gilberto.nunes@selbetti.com.br>
To: Jordi Pujol <jordipujolp@gmail.com>
Cc: Gene Heskett <gene.heskett@gmail.com>,
Mike Galbraith <efault@gmx.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Galbraith patch
Date: Fri, 19 Nov 2010 15:11:24 -0200 [thread overview]
Message-ID: <1290186684.3189.5.camel@note-311a> (raw)
In-Reply-To: <201011191749.14781.jordipujolp@gmail.com>
HI...
I have compile a kernel 2.6.36 with autogroup but I don't see
any /proc/sys/kernel/sched_autogroup_enabled
Also, I tried with noautogroup and autogroup on kernel line boot, but it
doesn't work...
Maybe I do samething wrong...
Em Sex, 2010-11-19 às 17:49 +0100, Jordi Pujol escreveu:
> A Divendres 19 Novembre 2010 16:05:12, Gene Heskett va escriure:
> > Thanks Jordi, but my last attempted build, using only the last 2 patches
> > that Mike posted on a fresh unpack of 2.6.36, couldn't get past stage 2 of
> > the modules build, it kept squawking about all the IR control stuff that
> > is not even configured to be built.
> >
> > I wonder how long it will take to get work this into mainline?
> >
> > Along the same line, how does this compare to CK's bfs patch?
>
> the autogroup-sched patch works well, right now writing this message from a
> computer that runs that kernel.
>
> this patch is much simpler than CK2, so I suppose that the implementation
> should be more easy,
> I am trying both and observe, from my user's point of view, that they give a
> similar result.
>
> Gene, if that may help to do your own kernel implementation, the Debian kernel
> sources I've used are available at:
> http://livenet.selfip.com/ftp/debian/linux-2.6/
>
> 2.6.36 + CK2, in the subdirectory
> linux-2.6.36-0.jpp.10-lnet/
> 2.6.36 + autogroup_sched, in the subdirectory
> linux-2.6.36-0.jpp.11-lnet/
>
> Jordi Pujol
>
> Live never ending Tale
> GNU/Linux Live forever!
> http://livenet.selfip.com
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
--
Gilberto Nunes
Departamento de TI
Selbetti Gestão de Documentos
Fone: (47) 3441-6004
Celular (47) 8861-6672
<><
next prev parent reply other threads:[~2010-11-19 17:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 18:35 Galbraith patch Gilberto Nunes
2010-11-17 18:58 ` Dhaval Giani
2010-11-17 18:59 ` Dhaval Giani
2010-11-17 19:00 ` Dhaval Giani
2010-11-17 19:22 ` Gilberto Nunes
[not found] ` <1290021497.4887.24.camel@note-311a>
2010-11-17 23:21 ` Mike Galbraith
2010-11-17 23:36 ` Gilberto Nunes
2010-11-18 15:43 ` Gilberto Nunes
2010-11-18 16:06 ` Mike Galbraith
2010-11-18 16:40 ` Gilberto Nunes
2010-11-18 18:40 ` Thomas Backlund
2010-11-18 19:35 ` Gene Heskett
2010-11-18 20:10 ` Mike Galbraith
2010-11-18 21:29 ` Gene Heskett
2010-11-18 20:00 ` Mike Galbraith
2010-11-18 21:16 ` Thomas Backlund
2010-11-18 21:36 ` Gene Heskett
2010-11-18 21:28 ` Gene Heskett
2010-11-18 22:29 ` Thomas Backlund
2010-11-19 14:09 ` Jordi Pujol
2010-11-19 15:05 ` Gene Heskett
2010-11-19 16:21 ` Mike Galbraith
2010-11-20 0:05 ` Gene Heskett
2010-11-19 16:49 ` Jordi Pujol
2010-11-19 17:11 ` Gilberto Nunes [this message]
2010-11-19 16:09 ` Mike Galbraith
2010-11-18 19:32 ` Gene Heskett
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=1290186684.3189.5.camel@note-311a \
--to=gilberto.nunes@selbetti.com.br \
--cc=efault@gmx.de \
--cc=gene.heskett@gmail.com \
--cc=jordipujolp@gmail.com \
--cc=linux-kernel@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