From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: ** X-Spam-Status: No, score=2.5 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 03576C18E5B for ; Tue, 17 Mar 2020 10:11:09 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id BD975205ED for ; Tue, 17 Mar 2020 10:11:08 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="bdaQ8gvT" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BD975205ED Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.92.3) (envelope-from ) id 1jE9B5-0003I6-Sp; Tue, 17 Mar 2020 06:10:27 -0400 Received: from mail-ed1-x531.google.com ([2a00:1450:4864:20::531]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from ) id 1jE9B3-0003Hy-QO for kernelnewbies@kernelnewbies.org; Tue, 17 Mar 2020 06:10:25 -0400 Received: by mail-ed1-x531.google.com with SMTP id z3so7988741edq.11 for ; Tue, 17 Mar 2020 03:10:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dv2z5zJFHwYQIzdp3UQVEj6khiGgTuTKP52p6MWRADw=; b=bdaQ8gvT60uX58O+xjz/RvwfNxzxKDi6V572A8Kdghr3v5oguY3umJLLCHwrV8Q7JN bAY+sTCtgXLJYedDy+3/jx5jR82ldnkD+rivEIhSDU2dQDc8qxd1kmXBXizLz9q+Wlys VgnyzHdMZebnSr1liXpIDOPSeat94QVkg5Us905SKA6ohc5Cw+87Beu+SG9Xa64OGkP+ mGj6E1caRZ1iudw6SDmSnOC8MhGEtJqs9Fbg8y6FDp4vgL2ouD9c+Rpm1mAHXn3osW09 Omj0UdxGNtYXjkwpc7Wri6JYpP4pTFIBeAaj3Atf8vO/NFHulmAjLnPWWARxgrs25bKZ HbEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dv2z5zJFHwYQIzdp3UQVEj6khiGgTuTKP52p6MWRADw=; b=DuwSFL1ZIO9EfO1/yrmsQjn+mfpn5lz6DroXzQBhQ6d4/rE3KGtpCD68zDKdeWDj+y Ec6Gx/sIIWtuf6FUQpO/7+QYu7jdA5L8TaObMskUsOOJiXAdgqUXxGRq29+VdliEtLFN DTMsL0YkYiStniBOHurpsKBEGydH5wXwH95ASIyr79xFYefpITeKARqDojwaX1QRs3PG Rt7URqPSbrGB+XrGLu96wW38hhYo7IfiZ25M0MseHc/FbHXQ3F+6RfLcOqqQ5+HVO01X ECK9VLvHFpk+U+MQ4uh4vP2guBWdSDIrVns3cFCLpO3KGO1YV/SoMQRHHbVHKkeNG2rU dJLQ== X-Gm-Message-State: ANhLgQ0+PWGEd1aqJA0eHwzazwsuofDrRjpJtJPRbbkaKdPT5oP+G3yj 6G8TCRdhDM8ufMvEc/qJX7mzq0aEPHXDYgJjd8Y= X-Google-Smtp-Source: ADFU+vtMXXDiCwupTjo8CAs3ALnPBTjPNKsUA5DiXWSOmBym7DgI0cbLSIzfVQX9GK7uLfuh8zBMabMH1isS+EgJrBY= X-Received: by 2002:a17:906:1a0c:: with SMTP id i12mr3563527ejf.124.1584439822428; Tue, 17 Mar 2020 03:10:22 -0700 (PDT) MIME-Version: 1.0 References: <798884.1584436389@turing-police> In-Reply-To: <798884.1584436389@turing-police> From: suvrojit Date: Tue, 17 Mar 2020 15:40:10 +0530 Message-ID: Subject: Re: To: =?UTF-8?Q?Valdis_Kl=C4=93tnieks?= Cc: kernelnewbies@kernelnewbies.org, Sankalp Bhardwaj X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9135774580375902057==" Errors-To: kernelnewbies-bounces@kernelnewbies.org --===============9135774580375902057== Content-Type: multipart/alternative; boundary="000000000000c8ad4f05a10a2459" --000000000000c8ad4f05a10a2459 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ULK by Bovet Cessati is the book u should start reading Sankalp On Tue, Mar 17, 2020, 2:44 PM Valdis Kl=C4=93tnieks wrote: > On Tue, 17 Mar 2020 04:37:58 +0530, Sankalp Bhardwaj said: > > > Where to get started?? I am interested in understanding how the > > kernel works but have no prior knowledge... Please help!! > > A good place to start is to realize that the answers often depend on what > the > question is - and there's usually a difference between the question that = is > asked, and the question that the person needs the answer for. You probab= ly > want to read this: > > > https://lists.kernelnewbies.org/pipermail/kernelnewbies/2017-April/017765= .html > > Something that you'll need is a good understanding of operating system > concepts. Almost all modern computer systems have some idea of basic > concepts > such as processes, files, a directory structure, security and permissions= , > scheduling, locking, and so on. And for most of these, there is more tha= n > one > way to accomplish the goal. > > So two books that are useful to read for a compare-and-contrast view are > Bach's > book on the System V kernel, and McKusic's book on the BSD kernel - both = go > into details of *why* some things are done they are. It's really helpful > to > see stuff like "We need to lock this inode while we do X, because otherwi= se > another thread could concurrently do Y, and then Bad Thing Z will happen"= . > > Of course, a Linux filesystem that does things differently won't have the > same > exact issues, but understanding the *sort* of things that break when you > screw > up your locking is quite the useful info, especially if most of your > coding has > been in userspace where single-threaded is common and libraries did their > own > locking when needed. > > I admit that I also learned a bunch from Tanenbaum's "Modern Operating > Systems", but that was a long long time ago in a galaxy far far away, and= I > have no idea what the cool kids are reading instead these days... > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > --000000000000c8ad4f05a10a2459 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
ULK by Bovet Cessati is the book u should start reading S= ankalp

On Tue, Mar 17, 2020, 2:44 PM Valdis Kl=C4=93tnieks <valdis.kletnieks@vt.edu> wrote:
On Tue, 17 Mar 2020 04:37:58 +0530, Sanka= lp Bhardwaj said:

> Where to get started?? I am interested in understanding how the
> kernel works but have no prior knowledge... Please help!!

A good place to start is to realize that the answers often depend on what t= he
question is - and there's usually a difference between the question tha= t is
asked, and the question that the person needs the answer for.=C2=A0 You pro= bably
want to read this:

https://lis= ts.kernelnewbies.org/pipermail/kernelnewbies/2017-April/017765.html

Something that you'll need is a good understanding of operating system<= br> concepts. Almost all modern computer systems have some idea of basic concep= ts
such as processes, files, a directory structure, security and permissions,<= br> scheduling, locking, and so on.=C2=A0 And for most of these, there is more = than one
way to accomplish the goal.

So two books that are useful to read for a compare-and-contrast view are Ba= ch's
book on the System V kernel, and McKusic's book on the BSD kernel - bot= h go
into details of *why* some things are done they are.=C2=A0 It's really = helpful to
see stuff like "We need to lock this inode while we do X, because othe= rwise
another thread could concurrently do Y, and then Bad Thing Z will happen&qu= ot;.

Of course, a Linux filesystem that does things differently won't have t= he same
exact issues, but understanding the *sort* of things that break when you sc= rew
up your locking is quite the useful info, especially if most of your coding= has
been in userspace where single-threaded is common and libraries did their o= wn
locking when needed.

I admit that I also learned a bunch from Tanenbaum's "Modern Opera= ting
Systems", but that was a long long time ago in a galaxy far far away, = and I
have no idea what the cool kids are reading instead these days...

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies= .org/mailman/listinfo/kernelnewbies
--000000000000c8ad4f05a10a2459-- --===============9135774580375902057== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============9135774580375902057==--