Skip to content

Conversation

@mysterywolf
Copy link
Member

@mysterywolf mysterywolf commented Jul 6, 2021

拉取/合并请求描述:(PR description)

[
信号量、消息队列、消息邮箱其FIFO功能,还有保留的意义。但是互斥量的FIFO没有任何存在的意义。
互斥量诞生之初就是为了解决信号量带来的无界优先级反转问题(Sha, 1990),而FIFO flag却恰恰人为引入了无界优先级反转的问题,这与互斥量的出现目的背道而驰。

再想一个问题,请问互斥量的FIFO和信号量的FIFO 有什么区别呢,答案是没有任何区别,那么直接用信号量的FIFO好不好呢?

因此解决方法为直接移除FIFO flag,无论用户选择FIFO 还是PRIO 一律按照PRIO处理。
]

以下的内容不应该在提交PR时的message修改,修改下述message,PR会被直接关闭。请在提交PR后,浏览器查看PR并对以下检查项逐项check,没问题后逐条在页面上打钩。
The following content must not be changed in the submitted PR message. Otherwise, the PR will be closed immediately. After submitted PR, please use a web browser to visit PR, and check items one by one, and ticked them if no problem.

当前拉取/合并请求的状态 Intent for your PR

必须选择一项 Choose one (Mandatory):

  • 本拉取/合并请求是一个草稿版本 This PR is for a code-review and is intended to get feedback
  • 本拉取/合并请求是一个成熟版本 This PR is mature, and ready to be integrated into the repo

代码质量 Code Quality:

我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:

  • 已经仔细查看过代码改动的对比 Already check the difference between PR and old code
  • 代码风格正确,包括缩进空格,命名及其他风格 Style guide is adhered to, including spacing, naming and other styles
  • 没有垃圾代码,代码尽量精简,不包含#if 0代码,不包含已经被注释了的代码 All redundant code is removed and cleaned up
  • 所有变更均有原因及合理的,并且不会影响到其他软件组件代码或BSP All modifications are justified and not affect other components or BSP
  • 对难懂代码均提供对应的注释 I've commented appropriately where code is tricky
  • 本拉取/合并请求代码是高质量的 Code in this PR is of high quality
  • 本拉取/合并符合RT-Thread代码规范 This PR complies with RT-Thread code specification

@Guozhanxin Guozhanxin added the +1 Agree +1 label Jul 7, 2021
@BernardXiong BernardXiong merged commit 7c00795 into RT-Thread:master Jul 7, 2021
@mysterywolf mysterywolf deleted the rmovefifo branch July 7, 2021 12:24
@mysterywolf mysterywolf mentioned this pull request Jan 20, 2022
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

+1 Agree +1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants