From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 124389 invoked by alias); 25 Nov 2017 03:50:28 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 124377 invoked by uid 89); 25 Nov 2017 03:50:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=BAYES_40,FREEMAIL_FROM,KB_WAM_FROM_NAME_SINGLEWORD,RCVD_IN_BL_SPAMCOP_NET,SPF_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=H*Ad:U*ecos-discuss, 163com, 163.com, H*r:Coremail X-HELO: m50-138.163.com Received: from m50-138.163.com (HELO m50-138.163.com) (123.125.50.138) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 25 Nov 2017 03:50:26 +0000 Received: from [10.8.8.4] (unknown [209.58.129.97]) by smtp1 (Coremail) with SMTP id C9GowAAXHwtz6BhaT_oDAA--.2S2; Sat, 25 Nov 2017 11:50:22 +0800 (CST) From: "cameled@163.com" To: ecos-discuss@sourceware.org Message-ID: <4e4fd801-6078-37e5-b7d7-c29ac2885e89@163.com> Date: Sat, 25 Nov 2017 03:50:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-CM-TRANSID:C9GowAAXHwtz6BhaT_oDAA--.2S2 X-Coremail-Antispam: 1Uf129KBjvdXoW7XFWDKrWfCr13ur1xGF4fGrg_yoWfWFX_Za yUGFn5GF42qrZ2vw4ayFs3uFWrGan7uFyjv3s5Xay3Gwn8AFn8XF9xZrykAa13Jw4aqrn8 Ar4YvFsYq34S9jkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUvcSsGvfC2KfnxnUUI43ZEXa7IUY_xhJUUUUU== X-CM-SenderInfo: pfdpvzlhg6il2tof0z/1tbiRR6buVl9hqZV4gAAsK Subject: [ECOS] eCos Document confirm X-SW-Source: 2017-11/txt/msg00003.txt.bz2 Hello, everyone Recnetly, I join eCos development. The offical document is a good start place, really useful for me. In kernel overview, its introduced system scheduler work behave. I have some confuse, it's may conflict to the source code. Document (ecos-v3.0-ref-letter.pdf) says the scheduler (MLQ) schedule same priority thread as LIFO (The eCos kernel->Kernel Overview ->Schedulers). After read the source code, I'm confuse. If I'm not wrong, source code now schedule it as FIFO(using add_tail and rem_head). I also found some in the ChangeLog at below. May be I'm wrong, anyone can help me about this?   2000-05-20  Jonathan Larmour        (Cyg_SchedulerThreadQueue_Implementation::enqueue): Add, like old       one, except make it FIFO instead of LIFO by inserting at end of queue As saying before, I'm new guy. Thanks for your work. Best wish.         cameled -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss