lwip-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [task #7212] Add Mutex concept in sys_arch


From: Frédéric Bernon
Subject: [lwip-devel] [task #7212] Add Mutex concept in sys_arch
Date: Wed, 15 Aug 2007 21:49:28 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6

URL:
  <http://savannah.nongnu.org/task/?7212>

                 Summary: Add Mutex concept in sys_arch
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: fbernon
            Submitted on: mercredi 15.08.2007 à 23:49
                Category: None
         Should Start On: mercredi 15.08.2007 à 00:00
   Should be Finished on: mercredi 15.08.2007 à 00:00
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None
                  Effort: 0.00

    _______________________________________________________

Details:

I would like to know your point of view about the fact to add the "mutex"
concept in sys_arch (in a post-1.3.0)?

There is already the sys_arch_protect/sys_arch_unprotect feature, which could
be very useful since like it's said in sys_arch.txt "...This function should
support recursive calls from the same task or interrupt. In other words,
sys_arch_protect() could be called while already protected...". But there is a
limitation since the "protect" is global, and we can have several ones in the
source code. More, since this one is global, it can be used for locking the
core. Actually, most of semaphores in the code are used like mutex...

Your comments ?




    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?7212>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.nongnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]