kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: xerofoify@gmail.com (Nick Krause)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Formula One Scheduler (was Re: Help with git)
Date: Fri, 8 Aug 2014 16:46:41 -0400	[thread overview]
Message-ID: <CAPDOMVgT=-GUdqRs8CfMdBiXH6k2YG6cFz0XZ6m9092ERCc1xg@mail.gmail.com> (raw)
In-Reply-To: <20140808202845.GA29247@worldash.org>

On Fri, Aug 8, 2014 at 4:28 PM, Arlie Stephens <arlie@worldash.org> wrote:
> On Aug 08 2014, Valdis.Kletnieks at vt.edu wrote:
>> There's a big difference between knowing how to change the spark plugs on
>> a VW Beetle, and being able to walk into a Formula One pit and make tuning
>> suggestions that actually help the performance.
>>
>> And yes, there's *that* big a gap between the usual beginner programmer
>> and some parts of the kernel.  In fact, I'll go out on a limb and say that
>> there are more people in this world that really understand Formula One
>> engines than people who really understand the Linux scheduler. :)
>
> Now that's depressing.
>
> --
> Arlie
>
> (Arlie Stephens                                 arlie at worldash.org)
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


That is kind of depressing. Is there any maintainers who want to
mentor me with the scheduler and other areas of interest.
I am willing to listen , I will just like a mentor to help me out :).
Nick

  reply	other threads:[~2014-08-08 20:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08  1:48 Help with git Nick Krause
2014-08-08  1:52 ` Kristofer Hallin
2014-08-08  1:58   ` Nick Krause
2014-08-08  1:59     ` Nick Krause
2014-08-08  2:00 ` Valdis.Kletnieks at vt.edu
2014-08-08  2:01   ` Nick Krause
2014-08-08  2:18     ` Sudip Mukherjee
2014-08-08  2:25       ` Nick Krause
2014-08-08  3:03         ` Valdis.Kletnieks at vt.edu
2014-08-08  3:05         ` Valdis.Kletnieks at vt.edu
2014-08-08  3:13           ` Nick Krause
2014-08-08 17:04             ` Nick Krause
2014-08-08 17:30               ` Nuno Martins
2014-08-08 17:37                 ` Nick Krause
2014-08-08 18:07                   ` Greg Freemyer
2014-08-08 18:16                     ` Kristofer Hallin
2014-08-08 18:28                       ` Robert P. J. Day
2014-08-08 18:31                         ` Kristofer Hallin
2014-08-08 18:18                     ` Nick Krause
2014-08-08 18:28                       ` Valdis.Kletnieks at vt.edu
2014-08-08 18:26                   ` Valdis.Kletnieks at vt.edu
2014-08-08 17:39               ` Valdis.Kletnieks at vt.edu
2014-08-08 17:53                 ` Nick Krause
2014-08-08 18:25                   ` Valdis.Kletnieks at vt.edu
2014-08-08 20:28                     ` Formula One Scheduler (was Re: Help with git) Arlie Stephens
2014-08-08 20:46                       ` Nick Krause [this message]
2014-08-09  5:23                         ` Sudip Mukherjee
2014-08-09 12:43                           ` Lidza Louina
2014-08-09  0:17                       ` Valdis.Kletnieks at vt.edu
2014-08-09 13:01                         ` Philipp Muhoray

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='CAPDOMVgT=-GUdqRs8CfMdBiXH6k2YG6cFz0XZ6m9092ERCc1xg@mail.gmail.com' \
    --to=xerofoify@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).