From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16493 invoked by alias); 9 Jun 2006 09:19:47 -0000 Received: (qmail 16484 invoked by uid 22791); 9 Jun 2006 09:19:46 -0000 X-Spam-Check-By: sourceware.org Received: from py-out-1112.google.com (HELO py-out-1112.google.com) (64.233.166.180) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 09 Jun 2006 09:19:43 +0000 Received: by py-out-1112.google.com with SMTP id d80so768218pyd for ; Fri, 09 Jun 2006 02:19:41 -0700 (PDT) Received: by 10.35.106.15 with SMTP id i15mr2318097pym; Fri, 09 Jun 2006 02:19:41 -0700 (PDT) Received: from taurus ( [82.100.245.2]) by mx.gmail.com with ESMTP id b43sm1569017pyb.2006.06.09.02.19.38; Fri, 09 Jun 2006 02:19:40 -0700 (PDT) Message-ID: <000701c68ba5$a56bd4d0$ea14a8c0@taurus> From: "Monica Dsz" To: "Gary Thomas" Cc: "ecos discuss" References: <000501c68b1a$68b523b0$ea14a8c0@taurus> <1149789900.15359.183.camel@hermes> Date: Fri, 09 Jun 2006 09:19:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] why is it wrong to call cyg_semaphore_post() in ISR??? X-SW-Source: 2006-06/txt/msg00092.txt.bz2 > It's a trade off - do you prevent interrupts (hence ISR routines) from > running during all data critical sections or do you simply not allow > those [ISR] functions to execute code that might perturb critical data? > eCos chooses the latter method which allows for lower interrupt latency > by putting off things until the DSR can be safely run. > just to confirm my understanding, does this mean that we never have to disable and re-enable the interrupts during critical sections? or are there any cases still we have to disable the interrupts in eCos. The more I try to understand eCos, the more I am liking it. I wonder why our company wasnt using this cool RTOS, anyway!!! I hope I will be able to convince my supervisor to use eCos instead of expensive VxWorks. Thanks again for the information. monica -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss