Re: [Nbd] Using nbd on Android
- To: Wouter Verhelst <w@...112...>
- Cc: nbd-general@lists.sourceforge.net
- Subject: Re: [Nbd] Using nbd on Android
- From: Brandon Amos <bamos@...1755...>
- Date: Mon, 22 Sep 2014 07:27:20 -0400
- Message-id: <DE4CF561-39DE-4C1D-AC0D-40F56789A6C5@...1755...>
- In-reply-to: <20140922075132.GB26345@...3...>
- References: <2236EE6B-0E9D-43A0-B8B4-89F85EC171AE@...1755...> <20140922075132.GB26345@...3...>
Hi Wouter,
> I see you needed to disable use of mlockall() for that. Care to send a
> patch? This should preferably check for existence of mlockall() in
> configure, and #ifdef it away if it's not present.
Sure, I'm happy to send in a patch for this.
Do you want me to add checks so that the `-swap` option is disabled
completely in Android, or just to disable the `mlockall` call and throw a
warning when starting with the swap option on Android?
The Tor bug tracker has a useful post on this:
https://trac.torproject.org/projects/tor/ticket/1147
> I also noticed you used qemu-nbd rather than nbd-server. Any particular
> reason for that?
I'm using nbd with a larger project that uses a custom version of qemu-nbd
to intercept block device writes. I'm not sure why qemu-nbd was
chosen in place of nbd-server.
-Brandon.
Reply to: