Re: ENBD and swap

> All that enbd does is lock the client code in RAM when you run with
> "-s". Then the client cannot be swapped out. After that it's up to
> you and the kernel!
> 
> Now, if you are using a tcp transport, then tcp will use buffers to deal
> with out of order packets, fragmentation, and so on. If RAM is full,
> then the kernel must swap something out to get memory for the buffers.
> Unfortunately, if swap is over tcp, you are stuck.

Would it be possible to preallocate all the memory TCP would ever need
and lock it in memory?

I'm sorry but I don't have knowledge about your other questions
(syncing, non-blocking etc.).

// Dag Sverre