This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Question about ecos server performance


On Tue, 2002-08-13 at 08:03, NavEcos wrote:
> [SNIP]
> > > The bug is as follows:
> > >
> > > 1) The server (eCos app) starts,
> > > 2) Connect to the server with telnet, port 4000
> >
> > Then what?  What do you have to do [from the "client" side] to
> > evoke the crash?
> 
> Connect.  That's all.  My crash happens in less than 3000 bytes
> of transferred data, always.
> 
> If you want, I can send you my entire environment but before I
> do that I'll update CVS.  Maybe it was a bad day when I downloaded?
> 

No, I was able to duplicate this.  I just asked before trying it as
I didn't want to waste time if there was more that was necessary.

The problem is obvious and, indeed, the program tells you exactly why.
It's reporting "too many mbufs to tx", which comes from the logical
network layer which tries to pack up a packet to be sent and give it
to the physical driver.  However, in this case, the data structure which
represents the packet has [perhaps] hundreds of little tiny pieces in
it.  The method used by the physical layer can't handle that 
[currently].  I'll have to think a bit about how to fix this.

I would say that this is a aberrant program though and just happened to
run into this limitation. 

-- 
------------------------------------------------------------
Gary Thomas                  |
eCosCentric, Ltd.            |  
+1 (970) 229-1963            |  eCos & RedBoot experts
gthomas@ecoscentric.com      |
http://www.ecoscentric.com/  |
------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]