search for: besically

i just install the Ruby on Rails 2.1.0..... But i faced lots of problem.... is there any way to install Ruby On Rails 2.0.2 thanking you --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org

...OOM handler is frowned upon, but it really is what we > need for this feature. > > Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we > could actually skip sending deflation requests to our hypervisor, > making the OOM path *very* simple. Besically freeing pages and > updating the balloon. If the communication with the host ever > becomes a problem on this call path. > @Michael, how to proceed with this? -- Thanks, David / dhildenb

...OOM handler is frowned upon, but it really is what we > need for this feature. > > Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we > could actually skip sending deflation requests to our hypervisor, > making the OOM path *very* simple. Besically freeing pages and > updating the balloon. If the communication with the host ever > becomes a problem on this call path. > @Michael, how to proceed with this? -- Thanks, David / dhildenb

...OOM handler is frowned upon, but it really is what we > need for this feature. > > Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we > could actually skip sending deflation requests to our hypervisor, > making the OOM path *very* simple. Besically freeing pages and > updating the balloon. If the communication with the host ever > becomes a problem on this call path. > > [1] https://www.spinics.net/lists/linux-virtualization/msg40863.html > > Reported-by: Tyler Sanderson <tysand at google.com> > Cc:...

...ry via leak_balloon(); leak_balloon: wait for balloon_lock to be released by fill_balloon. > Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we > could actually skip sending deflation requests to our hypervisor, > making the OOM path *very* simple. Besically freeing pages and > updating the balloon. Well not exactly. !VIRTIO_BALLOON_F_MUST_TELL_HOST does not actually mean "never tell host". It means "host will not discard pages in the balloon, you can defer host notification until after use". This was the original implem...

...ry via leak_balloon(); leak_balloon: wait for balloon_lock to be released by fill_balloon. > Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we > could actually skip sending deflation requests to our hypervisor, > making the OOM path *very* simple. Besically freeing pages and > updating the balloon. Well not exactly. !VIRTIO_BALLOON_F_MUST_TELL_HOST does not actually mean "never tell host". It means "host will not discard pages in the balloon, you can defer host notification until after use". This was the original implem...

Two fixes for issues I stumbled over while working on patch #3. Switch back to the good ol' OOM handler for VIRTIO_BALLOON_F_DEFLATE_ON_OOM as the switch to the shrinker introduce some undesired side effects. Keep the shrinker in place to handle VIRTIO_BALLOON_F_FREE_PAGE_HINT. Lengthy discussion under [1]. I tested with QEMU and "deflate-on-oom=on". Works as expected. Did not test

...e OOM handler is frowned upon, but it really is what we > need for this feature. > > Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we > could actually skip sending deflation requests to our hypervisor, > making the OOM path *very* simple. Besically freeing pages and > updating the balloon. If the communication with the host ever > becomes a problem on this call path. > > [1] https://www.spinics.net/lists/linux-virtualization/msg40863.html > > Reported-by: Tyler Sanderson <tysand at google.com> > Cc: Mi...

...e OOM handler is frowned upon, but it really is what we > need for this feature. > > Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we > could actually skip sending deflation requests to our hypervisor, > making the OOM path *very* simple. Besically freeing pages and > updating the balloon. If the communication with the host ever > becomes a problem on this call path. > > [1] https://www.spinics.net/lists/linux-virtualization/msg40863.html > > Reported-by: Tyler Sanderson <tysand at google.com> > Cc: Mi...

...> need for this feature. >> > > >> > > Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we >> > > could actually skip sending deflation requests to our hypervisor, >> > > making the OOM path *very* simple. Besically freeing pages and >> > > updating the balloon. If the communication with the host ever >> > > becomes a problem on this call path. >> > > >> > >> > @Michael, how to proceed with this? >> > >> >> I'd like to...

...y. But I want to understand first, how something like that would even be possible. >> Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we >> could actually skip sending deflation requests to our hypervisor, >> making the OOM path *very* simple. Besically freeing pages and >> updating the balloon. > > Well not exactly. !VIRTIO_BALLOON_F_MUST_TELL_HOST does not actually > mean "never tell host". It means "host will not discard pages in the > balloon, you can defer host notification until after use". >...

...tify(). Note1: using the OOM handler is frowned upon, but it really is what we need for this feature. Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we could actually skip sending deflation requests to our hypervisor, making the OOM path *very* simple. Besically freeing pages and updating the balloon. If the communication with the host ever becomes a problem on this call path. [1] https://www.spinics.net/lists/linux-virtualization/msg40863.html Reported-by: Tyler Sanderson <tysand at google.com> Cc: Michael S. Tsirkin <mst at redha...

...ned upon, but it really is what we >> need for this feature. >> >> Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we >> could actually skip sending deflation requests to our hypervisor, >> making the OOM path *very* simple. Besically freeing pages and >> updating the balloon. If the communication with the host ever >> becomes a problem on this call path. >> >> [1] https://www.spinics.net/lists/linux-virtualization/msg40863.html >> >> Reported-by: Tyler Sanderson <tysand at...

...tify(). Note1: using the OOM handler is frowned upon, but it really is what we need for this feature. Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we could actually skip sending deflation requests to our hypervisor, making the OOM path *very* simple. Besically freeing pages and updating the balloon. If the communication with the host ever becomes a problem on this call path. [1] https://www.spinics.net/lists/linux-virtualization/msg40863.html Test report by Tyler Sanderson: Test setup: VM with 16 CPU, 64GB RAM. Running Debian 10. We have...

...tify(). Note1: using the OOM handler is frowned upon, but it really is what we need for this feature. Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we could actually skip sending deflation requests to our hypervisor, making the OOM path *very* simple. Besically freeing pages and updating the balloon. If the communication with the host ever becomes a problem on this call path. [1] https://www.spinics.net/lists/linux-virtualization/msg40863.html Test report by Tyler Sanderson: Test setup: VM with 16 CPU, 64GB RAM. Running Debian 10. We have...

...would even be possible. Hmm it looks like you are right. Sorry! > >> Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we > >> could actually skip sending deflation requests to our hypervisor, > >> making the OOM path *very* simple. Besically freeing pages and > >> updating the balloon. > > > > Well not exactly. !VIRTIO_BALLOON_F_MUST_TELL_HOST does not actually > > mean "never tell host". It means "host will not discard pages in the > > balloon, you can defer host notification unt...

...would even be possible. Hmm it looks like you are right. Sorry! > >> Note2: without VIRTIO_BALLOON_F_MUST_TELL_HOST (iow, always with QEMU) we > >> could actually skip sending deflation requests to our hypervisor, > >> making the OOM path *very* simple. Besically freeing pages and > >> updating the balloon. > > > > Well not exactly. !VIRTIO_BALLOON_F_MUST_TELL_HOST does not actually > > mean "never tell host". It means "host will not discard pages in the > > balloon, you can defer host notification unt...