From: damian.tometzki@icloud.com (Damian Tometzki)
To: kernelnewbies@lists.kernelnewbies.org
Subject: help in the MM Area of the Linux Kernel
Date: Fri, 06 Oct 2017 20:29:29 +0200 [thread overview]
Message-ID: <1507314569.1800.9.camel@icloud.com> (raw)
In-Reply-To: <5997.1507307670@turing-police.cc.vt.edu>
Hello Valdis,
thank you you for you reply. I'work for a big company as SAP partner
and i responsible for SAP HANA and the infrastucture.?
My personal intrest is the memory managment. My impression was the same
as you answerded.?
As you said i will try to figure out what the mm code is doing and try
to find out what can we do better.?
Damian
Am Freitag, den 06.10.2017, 12:34 -0400 schrieb
valdis.kletnieks at vt.edu:
> On Thu, 05 Oct 2017 18:14:08 +0200, Damian Tometzki said:
>
> >
> > i'am intrested in helping and Bug Fixing in the mm area of the
> > linux
> > kernel.?
> >
> > For driver development is it clear check in the staging area the
> > TODO's.?
> >
> > And what is the process for other areas of the kernel for example
> > mm
> > (Memory management X86) ??
> Rule 1 of kernel hacking:??Not every mechanic gets to work on Formula
> 1
> engines.
>
> For mm, you'll probably need to show some expertise in other kernel
> areas,
> *plus* have a deep understanding of memory management theory. That
> code has
> already been worked over by multiple professionals, which means
> pretty much all
> the easy stuff has already been done.
>
> Oh, and you're probably going to also need knowledge of the kernel
> instrumentation - perf, tracepoints, and friends.
>
> If you manage to find an actual bug in that code, it is most likely
> going to be
> some weird corner case, and *much* MM clue will be required to fix it
> without
> breaking some *other* more common corner case.??Remember that the
> same code has
> to Do The Right Thing on everything from an embedded system with 32M
> of RAM and
> only one major process running, to large mainframe class boxes with a
> terabyte
> of RAM, a large Oracle instance, and several hundred Apache / Tomcat
> / etc
> processes flickering in and out of existence, to multi-terabyte
> systems running
> HPC (where the use of RDMA over Infiniband by things like MPI creates
> challenges due to a *lot* of locked pages...)
>
> Your best bet???Find a replicable corner case (this may require
> access to a
> variety of systems), create a test-case that can cause the corner
> case on
> demand.??Figure out what the mm code is doing, and how it could do it
> better.
> Write a patch, test, and then double-check on other systems that you
> didn't
> cause a regression.??Submit the patch.
>
> Good luck. :)
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2017-10-06 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 16:14 help in the MM Area of the Linux Kernel Damian Tometzki
2017-10-06 14:19 ` Damian Tometzki
2017-10-06 14:31 ` Damian Tometzki
2017-10-06 16:34 ` valdis.kletnieks at vt.edu
2017-10-06 18:29 ` Damian Tometzki [this message]
2017-10-09 6:48 ` Ricardo Ribalda Delgado
2017-10-10 1:50 ` Yubin Ruan
2017-10-10 1:58 ` Jeffrey Walton
2017-10-10 2:56 ` valdis.kletnieks at vt.edu
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=1507314569.1800.9.camel@icloud.com \
--to=damian.tometzki@icloud.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).