Thread (12 messages) 12 messages, 6 authors, 2014-08-19

TCP/UDP

From: Nick Krause <hidden>
Date: 2014-08-18 17:29:46

On Mon, Aug 18, 2014 at 1:26 PM, Manish Katiyar [off-list ref] wrote:
On Mon, Aug 18, 2014 at 10:21 AM, Nick Krause [off-list ref] wrote:
quoted
On Mon, Aug 18, 2014 at 1:13 PM, Nick Krause [off-list ref] wrote:
quoted
On Mon, Aug 18, 2014 at 12:57 PM,  [off-list ref] wrote:
quoted
On Mon, 18 Aug 2014 12:25:53 -0400, Nick Krause said:
quoted
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:
quoted
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?
Valdis,
I was interested in both at the same time, just asked about
Beagle-boards first.
I aren't having any difficulty with it , I just wanted to known more
about this
area as the docs out there are terrible and not worth reading on this
part of
the networking stack.
Valdis,
In addition I generally learn 5 or 6 areas of a topic or program at
the same time so I
am just asking at different times. Just to make you and the other
developers have
an easier time I will paste my kernel interests below in a list.
Regards Nick
1. Networking
2. Usb, PCI , Networking and CPU Freq Drivers
3. Embedded Boards
4. Kernel Booting with UEFI(curiosity mostly)
5. Btrfs , F2FS ,NFS filesysems
6.  VFS
7. Process and Virtual Memory Subsystems
8. Memory Management

This is amusing :-). So when you wrote linux from scratch, did you implement
it in the following order too ?

Thanks -
Manish

quoted

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Of course not, just listing it off.
Nick
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help