1. 20 Jun, 2016 1 commit
  2. 19 Jun, 2016 3 commits
    • Paul Sokolovsky's avatar
    • Paul Sokolovsky's avatar
    • Paul Sokolovsky's avatar
      extmod/modlwip: Store a chain of incoming pbufs, instead of only one. · 5071ceea
      Paul Sokolovsky authored
      Storing a chain of pbuf was an original design of @pfalcon's lwIP socket
      module. The problem with storing just one, like modlwip does is that
      "peer closed connection" notification is completely asynchronous and out of
      band. So, there may be following sequence of actions:
      1. pbuf #1 arrives, and stored in a socket.
      2. pbuf #2 arrives, and rejected, which causes lwIP to put it into a
      queue to re-deliver later.
      3. "Peer closed connection" is signaled, and socket is set at such status.
      4. pbuf #1 is processed.
      5. There's no stored pbufs in teh socket, and socket status is "peer closed
      connection", so EOF is returned to a client.
      6. pbuf #2 gets redelivered.
      Apparently, there's no easy workaround for this, except to queue all
      incoming pbufs in a socket. This may lead to increased memory pressure,
      as number of pending packets would be regulated only by TCP/IP flow
      control, whereas with previous setup lwIP had a global overlook of number
      packets waiting for redelivery and could regulate them centrally.
  3. 18 Jun, 2016 10 commits
  4. 17 Jun, 2016 11 commits
  5. 16 Jun, 2016 6 commits
  6. 15 Jun, 2016 9 commits