From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5952 invoked by alias); 23 Oct 2002 02:43:28 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 5945 invoked from network); 23 Oct 2002 02:43:26 -0000 Message-ID: <3DB60CC9.3080601@eCosCentric.com> Date: Tue, 22 Oct 2002 19:43:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827 X-Accept-Language: en, en-us MIME-Version: 1.0 To: mohan lakshminarayan iyer CC: ecos-maintainers@sources.redhat.com Subject: Re: Zero Copy Networking References: <20021022165408.29202.qmail@webmail10.rediffmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-10/txt/msg00017.txt.bz2 mohan lakshminarayan iyer wrote: > Respected Sir, > We are final year of Computer Engineering students of University of > Pune,India. We would are interested in knowing more about eCos, if you > could tell us some source where material on eCos, particularly with > respect to memory management & the network stack, You have all the source, go for it :-). The net stack does have documentation. See http://www.vsr.si/ecos/ for example. As for memory management. eCos generally just sets up the MMU in a simple way. There's no protection between threads (i.e. no processes) nor separate address spaces. Although 3G Lab did some work on this for StrongARM: http://www.3glab.org/ > could be got it would > very helpful, also if you could tell us if Zero Copy Networking has been > implemented we would be grateful to you.Thanking You in anticipation. It hasn't. Jifl -- eCosCentric http://www.eCosCentric.com/ --[ "You can complain because roses have thorns, or you ]-- --[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine