Re: Enhance ramfs/zfs-less images

2017-11-22 Thread Nadav Har'El
On Wed, Nov 22, 2017 at 6:43 PM, Waldek Kozaczuk wrote: > I think that rather than implementing your suggestion which might not be > all that trivial I would rather implement some kind of proper LRU based > solution which would work like so: > This can work. Intererstingly, in the first patch wh

Re: Enhance ramfs/zfs-less images

2017-11-22 Thread Waldek Kozaczuk
Alternatively if the LRU cache idea is too complicated to implement we could instead have a simple hashmap by node-id type of cache with some TTL when memory buffer would be freed eventually. This would be unbounded inodes accessed count wise but it would be still limited to how big individual

Re: Enhance ramfs/zfs-less images

2017-11-22 Thread Waldek Kozaczuk
I think that rather than implementing your suggestion which might not be all that trivial I would rather implement some kind of proper LRU based solution which would work like so: - Every time mfs_read() called it would try to find corresponding buffer in it LRU cache (i-node is a key)

Re: I don't know how to use memcached image.

2017-11-22 Thread Nadav Har'El
On Wed, Nov 22, 2017 at 5:24 PM, Waldek Kozaczuk wrote: > You probably need to expose the port 1121 by adding forward option like so: > > scripts/run.py -e "memcached -u root" --forward "tcp:1121::1121" > Right. By default, run.py runs the image you just built (build/latest/usr.img) with qemu us

Re: I don't know how to use memcached image.

2017-11-22 Thread Waldek Kozaczuk
You probably need to expose the port 1121 by adding forward option like so: scripts/run.py -e "memcached -u root" --forward "tcp:1121::1121" On Tuesday, November 21, 2017 at 7:24:41 PM UTC-5, answe...@gmail.com wrote: > > I run Memcached image successfully, but I don't know how to use it. > > > w