[DRBD-user] Summarizing DRBD memory usage

Iustin Pop iustin at google.com
Thu Jul 24 13:49:29 CEST 2008

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On Thu, Jul 24, 2008 at 12:43:52PM +0200, Lars Ellenberg wrote:
> the max-buffer setting limits the abount of in-flight data.
> if nothing is in-flight, no such buffers are allocated.
> if something is in-flight, these are allocated on the receiving side
> to be able to submit it to the block device.
> 
> so "up to" max-buffers on the receiving side,
> which on the sending side corresponds to
> that many dirty (write-out) pages,
> or to pages read in by the resync process.
> 
> we also have a small number of mempools, and a page pool emergency
> reserve to not stall during write-out caused by hard memory pressure.

Ah, I see. Yes, I was looking at the 'worst-case' scenario. Thanks a
lot!

iustin



More information about the drbd-user mailing list