RE: Tux and TCP
"Collins, Tom" <[email protected]>
| Newsgroups | gmane.network.tux |
|---|---|
| Message-ID | <[email protected]> |
Hello... Thank you very much. Your comment about any socket-based protocol is exactly the interface that we have. It is entirely socket-based. We compile the kernel without CONFIG_INET enabled, so there are no protocol stacks where TUX would be running. Again, thanks Tom -----Original Message----- From: Ingo Molnar [mailto:[email protected]] Sent: Thursday, May 02, 2002 5:14 AM To: [email protected] Cc: Willman, Chad; Deaton, Larry; Beard, Derek Subject: Re: Tux and TCP On Thu, 2 May 2002, Collins, Tom wrote: > I am looking into the possibility of porting TUX to our hardware > platform. I was wondering what issues (performance or otherwise), lead > TUX to have such a heavy entanglement with TCP? it's not really entangled on any conceptual level, any socket-based networking protocol should be OK. Cleaning up TUX to get rid of TCP-only dependencies should not affect performance in any way. It should be as easy as fixing places that use a TCP-specific function instead of calling a generic socket-level handler (that is the same function in the TCP case). > A second (hopefully not a stupid) question: Is there any high-level > architecture document that explains how TUX functions? not that i'm aware of (the source code should be a pretty good reference though) - but i'll try to answer any design questions asked on this list. Ingo _______________________________________________ tux-list mailing list [email protected] https://listman.redhat.com/mailman/listinfo/tux-list ------------------------------- This e-mail is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review, use or disclosure is strictly prohibited. If you are not the intended recipient of this e-mail, please notify sender and delete all copies immediately.