[Top][All Lists]

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

[lwip-devel] [bug #51925] Replace the OOSEQ max bytes and pbufs constant

From: Joel Cunningham
Subject: [lwip-devel] [bug #51925] Replace the OOSEQ max bytes and pbufs constants with functions.
Date: Tue, 5 Sep 2017 10:02:45 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/603.3.8 (KHTML, like Gecko) Version/10.1.2 Safari/603.3.8

Follow-up Comment #1, bug #51925 (project lwip):

I took a look at your patch and I'm having trouble fully understanding how one
is supposed to implement TCP_OOSEQ_MAX_BYTES and TCP_OOSEQ_MAX_PBUFS since no
examples were provided.  They could return constants to maintain the current
behavior, but I want to understand the advantage this change provides

> For example, if the system only wants to allow the total number of rx pbufs
queued on all the ooseq lists to grow by one and a call is make indicating a
pcb already has two then it can return three for this call, but might return
one for another call - supporting a greedy allocation strategy. 

PCB isn't an input into the new functions, so how do you do this check?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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