All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa.com>
To: Michael Neuling <mikey@neuling.org>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Tickless Hz/hrtimers/etc. on PowerPC
Date: Thu, 12 Jul 2007 21:04:48 +0100	[thread overview]
Message-ID: <46968960.6090402@genesi-usa.com> (raw)
In-Reply-To: <29941.1184255383@neuling.org>

Michael Neuling wrote:
>> Okay.
>>
>> What I didn't want to do is spend a day sifting some other development
>> tree picking out what I think might be possibly sort of the right patches
>> for it.
>>
>> I'd get it wrong because having not worked on it, I don't know what I am
>> even looking for.
>>
>> And I don't want to run -rt or wireless-dev for the benefit of a single
>> feature. What I am after is something like Ingo Molnar throws out..
>> single patches done the old way, not git trees. It's so much easier to
>> handle and integrate for example into a Gentoo ebuild or to make a
>> tarball of accumulated patches from a certain release kernel.
> 
> I'm sooo with ya.  I like my patches alphabetised, but no one ever does
> it for me.

Well my only requirement is numbering them so they patch in order; there
are some cute little requirements on that, but I'd rather patch the bare
minimum and bring in as few quirks and new features than just grab an
entire -rt tree with what amounts to 60 or 70 individual patches and
start renumbering them.

We already have some ~20 for Efika support on top of 2.6.22 including
minor bugfixes and stuff, and the Gentoo genpatches stuff. I really want
to get a good start on CFS, hrtimers, dynticks and so on though and see
if we can push it to users and get out some decent testing and bug
reports. I think it will help everyone if it is not just a feature which
hits mainline after 6 months through supposed maturity (when a lack of
bug reports may well also be down to lack of interest).

I think the Efika as a low-power and fairly average performance board,
would benefit (and does benefit!) from features like dynticks, 5200B
has a bunch of hrtimers, SLUB gave me some insane speed improvement
exactly as the best benchmarks predicted (also got the same under VMware
on my x86 laptop, never going back to SLAB now!). The more processor
time we can eke out, and the less unecessary work the processor does
on housekeeping, the better the board will run for users. Everyone wins :)

-- 
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations

  reply	other threads:[~2007-07-12 20:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 18:06 Tickless Hz/hrtimers/etc. on PowerPC Matt Sealey
2007-07-11 18:17 ` Sergei Shtylyov
2007-07-11 18:33 ` Michael Neuling
2007-07-11 22:15   ` Matt Sealey
2007-07-12  6:41     ` Tony Breeds
2007-07-12 12:07       ` Matt Sealey
2007-07-16  0:45         ` Tony Breeds
2007-07-12 15:49     ` Michael Neuling
2007-07-12 20:04       ` Matt Sealey [this message]
2007-07-12 20:12         ` Geert Uytterhoeven
2007-07-13  8:34         ` Benjamin Herrenschmidt
2007-07-12 16:32     ` Sergei Shtylyov
2007-07-12 20:08       ` Matt Sealey
2007-07-12  6:51 ` Domen Puncer
2007-07-12 12:07   ` Matt Sealey
2007-07-13  8:41     ` Domen Puncer
2007-07-12 14:11   ` Sergei Shtylyov
2007-07-12 16:41     ` Sergei Shtylyov
2007-07-13  8:49     ` Domen Puncer

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=46968960.6090402@genesi-usa.com \
    --to=matt@genesi-usa.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mikey@neuling.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.