summaryrefslogtreecommitdiffstats
path: root/drivers/mfd/max8997.c
diff options
context:
space:
mode:
authorYing Xue <ying.xue@windriver.com>2012-11-15 04:34:45 +0100
committerPaul Gortmaker <paul.gortmaker@windriver.com>2012-11-22 02:07:25 +0100
commit3c294cb374bf7ad6f5c2763f994d75935fb7814d (patch)
treef85f567d4c69ae8dbbbdce32022d6f306cf7fc35 /drivers/mfd/max8997.c
parenttipc: wake up all waiting threads at socket shutdown (diff)
downloadlinux-3c294cb374bf7ad6f5c2763f994d75935fb7814d.tar.xz
linux-3c294cb374bf7ad6f5c2763f994d75935fb7814d.zip
tipc: remove the bearer congestion mechanism
Currently at the TIPC bearer layer there is the following congestion mechanism: Once sending packets has failed via that bearer, the bearer will be flagged as being in congested state at once. During bearer congestion, all packets arriving at link will be queued on the link's outgoing buffer. When we detect that the state of bearer congestion has relaxed (e.g. some packets are received from the bearer) we will try our best to push all packets in the link's outgoing buffer until the buffer is empty, or until the bearer is congested again. However, in fact the TIPC bearer never receives any feedback from the device layer whether a send was successful or not, so it must always assume it was successful. Therefore, the bearer congestion mechanism as it exists currently is of no value. But the bearer blocking state is still useful for us. For example, when the physical media goes down/up, we need to change the state of the links bound to the bearer. So the code maintaing the state information is not removed. Signed-off-by: Ying Xue <ying.xue@windriver.com> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Diffstat (limited to 'drivers/mfd/max8997.c')
0 files changed, 0 insertions, 0 deletions