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: dynamic allocation of memory during driver initializat ion?

From: Grant Edwards <grante at visi dot com>
To: Jay Foster <jay dot foster at systech dot com>,ecos-discuss at sources dot redhat dot com
Date: Fri, 8 Aug 2003 16:00:35 -0500
Subject: Re: [ECOS] dynamic allocation of memory during driver initializat ion?
References: <80B97DE95AEED311BA580050047FE98494F67A@mail.systech.com> <20030808154933.A11610@visi.com> <20030808205711.GC16737@londo.lunn.ch>

On Fri, Aug 08, 2003 at 10:57:11PM +0200, Andrew Lunn wrote:

> > I could add code to the DSRs to check to see if the
> > buffers have been allocated, and discard the data if they
> > haven't, but I was hoping to avoid make the DSRs any longer.
> 
> Do you really think 2 more machine instructions is that significant
> compared to all the other overheads of actually getting into and out
> of a DSR?

Probably not.

I guess it's the addition of more internal state to the thing
that "feels" bad rather than the actual length of the DSR.

-- 
Grant Edwards
grante@visi.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

References:
- RE: dynamic allocation of memory during driver initialization?
  - From: Jay Foster
- Re: dynamic allocation of memory during driver initializat ion?
  - From: Grant Edwards
- Re: dynamic allocation of memory during driver initializat ion?
  - From: Andrew Lunn

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