linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Krause <xerofoify@gmail.com>
To: Russell Coker <russell@coker.com.au>
Cc: "linux-btrfs@vger.kernel.org SYSTEM list:BTRFS FILE"
	<linux-btrfs@vger.kernel.org>
Subject: Re: Threads being NUMA aware
Date: Sun, 3 Aug 2014 23:52:48 -0400	[thread overview]
Message-ID: <CAPDOMVg_aRmukMTDpmwp48DyHt+_Ti7wO+94PbBqQCAhxB6Qnw@mail.gmail.com> (raw)
In-Reply-To: <1710836.KjMYxs0ugf@xev>

On Sun, Aug 3, 2014 at 11:42 PM, Russell Coker <russell@coker.com.au> wrote:
> On Sun, 3 Aug 2014 22:44:26 Nick Krause wrote:
>> On Sun, Aug 3, 2014 at 7:48 PM, Russell Coker <russell@coker.com.au> wrote:
>> > Please get yourself a NUMA system and test this out.
>>
>> Unfortunately I don't have money for an extra machine as of now as I
>> am a student
>
> If you can't get an extra machine then you probably can't contribute to
> developing filesystems, and your ability to do any sort of kernel development
> will be greatly limited.  It's probably best that you choose another area of
> software development until you get more hardware (and skill).
>
>> so if x86 is NUMA I can test otherwise I can't.
>
> If you had even read the NUMA Wikipedia page then you would already know the
> answer to this implied question.
>
> But really programming computers isn't something that you are good at.  It's
> not something that you will become good at if you attempt tasks that are way
> above your skill level.  I think that the best strategy for you is to find a
> mailing list for Linux beginners, when your skills get to the level that you
> answer more questions than you ask (and people appreciate your answers) then
> you can move on to easy programming tasks.  Once you master the easy
> programming tasks you can move on to more difficult tasks.
>
> I suggest that you develop a realistic plan.  Plan to start kernel programming
> in 2024 and have a series of goals on that path over the next 10 years.  Make
> your 2015 goal be answering lots of questions on a Linux beginners mailing
> list, that's a goal you can achieve in a year.
>
> --
> My Main Blog         http://etbe.coker.com.au/
> My Documents Blog    http://doc.coker.com.au/
>

After reading the article seems it does and just because I don't have
an extra machine doesn't seem to be an issue so
far.
Regards Nick

      reply	other threads:[~2014-08-04  3:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-03 18:53 Threads being NUMA aware Nick Krause
2014-08-03 23:48 ` Russell Coker
2014-08-04  2:44   ` Nick Krause
2014-08-04  3:42     ` Russell Coker
2014-08-04  3:52       ` Nick Krause [this message]

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=CAPDOMVg_aRmukMTDpmwp48DyHt+_Ti7wO+94PbBqQCAhxB6Qnw@mail.gmail.com \
    --to=xerofoify@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=russell@coker.com.au \
    /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).