kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: TCP/UDP
Date: Mon, 18 Aug 2014 12:57:20 -0400	[thread overview]
Message-ID: <25297.1408381040@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 18 Aug 2014 12:25:53 -0400." <CAPDOMVgNEB=Ua4GV2i6GxHf4gOKOnZCrGAXmCN=QEECyRUvOOg@mail.gmail.com>

On Mon, 18 Aug 2014 12:25:53 -0400, Nick Krause said:
> Hey Guys,
> After Searching the kernel Docs there is very little information on
> this for new developers. I want to know more about how
> the kernel code is written to handle TCP/UDP as even with Google and
> kernel programming books it's not good enough to
> learn how to write code for this particular subsystem at a high level.

Do we need to stick a "CAUTION: NO USER SERVICEABLE PARTS INSIDE" sticker
on there before you get the hint?

Let me quote a mail of yours from less than 24 hours ago:

> Further more I learn really fast  in my areas of interest, after my first year
> of programming I was already have build my own distro of Linux from Scratch,
> and after my second year was learning how to program embedded bootloaders and
> the like.  I am not lying this is no joke

If this is the truth, you should be having *zero* difficulty with
the Linux network stack.

Anyhow, I'm not feeling like digging up any good references for you,
because I have zero guarantee it's worth my time.  Beagleboads apparently
lasted all of 36 hours - why should I dig up references fo something that
you probably won't be interested in by the time I finish typing the mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140818/ee4c9070/attachment.bin 

  parent reply	other threads:[~2014-08-18 16:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 16:25 TCP/UDP Nick Krause
2014-08-18 16:51 ` TCP/UDP Afonso Bordado
2014-08-18 16:54   ` TCP/UDP Nick Krause
2014-08-18 16:57 ` Valdis.Kletnieks at vt.edu [this message]
2014-08-18 17:13   ` TCP/UDP Nick Krause
2014-08-18 17:21     ` TCP/UDP Nick Krause
2014-08-18 17:26       ` TCP/UDP Manish Katiyar
2014-08-18 17:29         ` TCP/UDP Nick Krause
2014-08-19  2:06     ` one thing at a time Rik van Riel
2014-08-19  2:55       ` Nick Krause
2014-08-19  2:59         ` Nick Krause
2014-08-19  4:25           ` Nick Krause
2014-08-19  6:29             ` Jason Ball
2014-08-19 12:13           ` Greg Freemyer
2014-08-19 16:41             ` Nick Krause
2014-08-18 17:31 ` TCP/UDP Denis Kirjanov
2014-08-18 17:33   ` TCP/UDP Nick Krause
2014-08-18 19:43     ` TCP/UDP Nick Krause
2014-08-19  0:46       ` fd type from number Loris Degioanni
2014-08-19 12:04         ` Greg Freemyer

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=25297.1408381040@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --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).