search for: trraverse

...to an array and incremented the array idex, and I'M DONE") - then in that workqueue entry that you start *anyway*, you empty the array and do all the crazy virtio stuff. In fact, while at it, just simplify the VM interface too. Instead of traversing a random number of buddy lists, just trraverse *one* - the top-level one. Are you seriously ever going to shrink or mark read-only anythin *but* something big enough to be in the maximum order? MAX_ORDER is what, 11? So we're talking 8MB blocks. Do you *really* want the balloon code to work on smaller things, particularly since the whole i...

...to an array and incremented the array idex, and I'M DONE") - then in that workqueue entry that you start *anyway*, you empty the array and do all the crazy virtio stuff. In fact, while at it, just simplify the VM interface too. Instead of traversing a random number of buddy lists, just trraverse *one* - the top-level one. Are you seriously ever going to shrink or mark read-only anythin *but* something big enough to be in the maximum order? MAX_ORDER is what, 11? So we're talking 8MB blocks. Do you *really* want the balloon code to work on smaller things, particularly since the whole i...

...gt; >>> - then in that workqueue entry that you start *anyway*, you empty the >>> array and do all the crazy virtio stuff. >>> >>> In fact, while at it, just simplify the VM interface too. Instead of >>> traversing a random number of buddy lists, just trraverse *one* - the >>> top-level one. Are you seriously ever going to shrink or mark >>> read-only anythin *but* something big enough to be in the maximum >>> order? >>> >>> MAX_ORDER is what, 11? So we're talking 8MB blocks. Do you *really* >>> wa...

On Mon, Jun 11, 2018 at 11:32 AM Linus Torvalds <torvalds at linux-foundation.org> wrote: > > So now we apparently do a GFP_KERNEL allocation insider the mm zone > lock, which is broken on just _so_ many levels. Oh, I see the comment about how it doesn't actually do an allocation at all because it's a single-entry. Still too damn ugly to live, and much too fragile. No way

On Mon, Jun 11, 2018 at 11:32 AM Linus Torvalds <torvalds at linux-foundation.org> wrote: > > So now we apparently do a GFP_KERNEL allocation insider the mm zone > lock, which is broken on just _so_ many levels. Oh, I see the comment about how it doesn't actually do an allocation at all because it's a single-entry. Still too damn ugly to live, and much too fragile. No way