search for: _bit_

...; > + vb->bmap_len = ALIGN(vb->pfn_limit, BITS_PER_LONG) / > + BITS_PER_BYTE + 2 * sizeof(unsigned long); > + hdr_len = sizeof(struct balloon_bmap_hdr); > + vb->bmap_hdr = kzalloc(hdr_len + vb->bmap_len, GFP_KERNEL); This ends up doing a 1MB kmalloc() right? That seems a _bit_ big. How big was the pfn buffer before?

...; > + vb->bmap_len = ALIGN(vb->pfn_limit, BITS_PER_LONG) / > + BITS_PER_BYTE + 2 * sizeof(unsigned long); > + hdr_len = sizeof(struct balloon_bmap_hdr); > + vb->bmap_hdr = kzalloc(hdr_len + vb->bmap_len, GFP_KERNEL); This ends up doing a 1MB kmalloc() right? That seems a _bit_ big. How big was the pfn buffer before?

..., BITS_PER_LONG) / > > > + BITS_PER_BYTE + 2 * sizeof(unsigned long); > > > + hdr_len = sizeof(struct balloon_bmap_hdr); > > > + vb->bmap_hdr = kzalloc(hdr_len + vb->bmap_len, GFP_KERNEL); > > > > This ends up doing a 1MB kmalloc() right? That seems a _bit_ big. > > How big was the pfn buffer before? > > > Yes I would limit this to 1G memory in a go, will result in a 32KByte bitmap. > > -- > MST Limit to 1G is bad for the performance, I sent you the test result several weeks ago. Paste it bellow: --------------------------...

..., BITS_PER_LONG) / > > > + BITS_PER_BYTE + 2 * sizeof(unsigned long); > > > + hdr_len = sizeof(struct balloon_bmap_hdr); > > > + vb->bmap_hdr = kzalloc(hdr_len + vb->bmap_len, GFP_KERNEL); > > > > This ends up doing a 1MB kmalloc() right? That seems a _bit_ big. > > How big was the pfn buffer before? > > > Yes I would limit this to 1G memory in a go, will result in a 32KByte bitmap. > > -- > MST Limit to 1G is bad for the performance, I sent you the test result several weeks ago. Paste it bellow: --------------------------...

...BITS_PER_LONG) / > > > + BITS_PER_BYTE + 2 * sizeof(unsigned long); > > > + hdr_len = sizeof(struct balloon_bmap_hdr); > > > + vb->bmap_hdr = kzalloc(hdr_len + vb->bmap_len, GFP_KERNEL); > > > > This ends up doing a 1MB kmalloc() right? That seems a _bit_ big. How big > > was the pfn buffer before? > > Yes, it is if the max pfn is more than 32GB. > The size of the pfn buffer use before is 256*4 = 1024 Bytes, it's too small, > and it's the main reason for bad performance. > Use the max 1MB kmalloc is a balance between...

...BITS_PER_LONG) / > > > + BITS_PER_BYTE + 2 * sizeof(unsigned long); > > > + hdr_len = sizeof(struct balloon_bmap_hdr); > > > + vb->bmap_hdr = kzalloc(hdr_len + vb->bmap_len, GFP_KERNEL); > > > > This ends up doing a 1MB kmalloc() right? That seems a _bit_ big. How big > > was the pfn buffer before? > > Yes, it is if the max pfn is more than 32GB. > The size of the pfn buffer use before is 256*4 = 1024 Bytes, it's too small, > and it's the main reason for bad performance. > Use the max 1MB kmalloc is a balance between...

...uable data, regardless of whether it was in the free list or not. The hypervisor only skips moving pages that were free *and* were never written to. So we never lose data, even if this "get free page info" stuff is totally out of date. The patch description and code comments are, um, a _bit_ light for this level of subtlety. :)

...uable data, regardless of whether it was in the free list or not. The hypervisor only skips moving pages that were free *and* were never written to. So we never lose data, even if this "get free page info" stuff is totally out of date. The patch description and code comments are, um, a _bit_ light for this level of subtlety. :)

...roup of me" ... and I have instructions for wbinfo to find that SID so I can ldbedit it. But you see my problem: wbinfo for finding SIDs is broke. Now... I've put my time into this. I've broken out ktrace and log level = 10. I've put a whole afternoon into this. Log stuff is a _bit_ interesting. When I wbinfo -i zbeeble, I get: [2016/07/11 01:10:37.408526, 1, pid=24476, effective(0, 0), real(0, 0)] ../librpc/ndr/ndr.c:439(ndr_print_function_debu g) wbint_LookupName: struct wbint_LookupName in: struct wbint_LookupName domain :...

On Thu, Jul 28, 2016 at 06:36:18AM +0000, Li, Liang Z wrote: > > > > This ends up doing a 1MB kmalloc() right? That seems a _bit_ big. > > > > How big was the pfn buffer before? > > > > > > Yes, it is if the max pfn is more than 32GB. > > > The size of the pfn buffer use before is 256*4 = 1024 Bytes, it's too > > > small, and it's the main reason for bad performance. &gt...

On Thu, Jul 28, 2016 at 06:36:18AM +0000, Li, Liang Z wrote: > > > > This ends up doing a 1MB kmalloc() right? That seems a _bit_ big. > > > > How big was the pfn buffer before? > > > > > > Yes, it is if the max pfn is more than 32GB. > > > The size of the pfn buffer use before is 256*4 = 1024 Bytes, it's too > > > small, and it's the main reason for bad performance. &gt...

...= ALIGN(vb->pfn_limit, BITS_PER_LONG) / > > + BITS_PER_BYTE + 2 * sizeof(unsigned long); > > + hdr_len = sizeof(struct balloon_bmap_hdr); > > + vb->bmap_hdr = kzalloc(hdr_len + vb->bmap_len, GFP_KERNEL); > > This ends up doing a 1MB kmalloc() right? That seems a _bit_ big. How > big was the pfn buffer before? Yes I would limit this to 1G memory in a go, will result in a 32KByte bitmap. -- MST

...= ALIGN(vb->pfn_limit, BITS_PER_LONG) / > > + BITS_PER_BYTE + 2 * sizeof(unsigned long); > > + hdr_len = sizeof(struct balloon_bmap_hdr); > > + vb->bmap_hdr = kzalloc(hdr_len + vb->bmap_len, GFP_KERNEL); > > This ends up doing a 1MB kmalloc() right? That seems a _bit_ big. How big > was the pfn buffer before? Yes, it is if the max pfn is more than 32GB. The size of the pfn buffer use before is 256*4 = 1024 Bytes, it's too small, and it's the main reason for bad performance. Use the max 1MB kmalloc is a balance between performance and flexibility, a...

...t > was in the free list or not. > > The hypervisor only skips moving pages that were free *and* were never > written to. So we never lose data, even if this "get free page info" > stuff is totally out of date. > > The patch description and code comments are, um, a _bit_ light for this level > of subtlety. :) I will add more description about this in v3. Thanks! Liang

> > > This ends up doing a 1MB kmalloc() right? That seems a _bit_ big. > > > How big was the pfn buffer before? > > > > Yes, it is if the max pfn is more than 32GB. > > The size of the pfn buffer use before is 256*4 = 1024 Bytes, it's too > > small, and it's the main reason for bad performance. > > Use the max 1MB km...

...gt; > > + BITS_PER_BYTE + 2 * sizeof(unsigned long); > > > > + hdr_len = sizeof(struct balloon_bmap_hdr); > > > > + vb->bmap_hdr = kzalloc(hdr_len + vb->bmap_len, GFP_KERNEL); > > > > > > This ends up doing a 1MB kmalloc() right? That seems a _bit_ big. > > > How big was the pfn buffer before? > > > > > > Yes I would limit this to 1G memory in a go, will result in a 32KByte bitmap. > > > > -- > > MST > > Limit to 1G is bad for the performance, I sent you the test result several weeks ago....

Hi, I'm new to this list. I tried to google and did a _bit_ of searching in teh archive but didn't find anything related to my problem. I use samba 2.2.8a as the PDC on SuSE-linux 8.0. I administrate 7 Rooms with 160 PC, mainly w2k-sp3 and some older with NT4-sp6. In two of seven rooms some PC loose their Domain-membership. I can bring them back into Do...

...f this "get free page info" > stuff is totally out of date. So if you include pages that were written to before the request then yes data will be lost. This is why we do this scan after we get the request and not e.g. on boot :) > The patch description and code comments are, um, a _bit_ light for this > level of subtlety. :) Add to that, for any page it is safe to skip and not add it to list. So the requirement is for when page must *not* be on this list: it must not be there if it is needed by guest but was not modified since the request. Calling it "free" will jus...

.... and I have instructions for wbinfo to find that SID so I can > ldbedit it. But you see my problem: wbinfo for finding SIDs is broke. > > Now... I've put my time into this. I've broken out ktrace and log level = > 10. I've put a whole afternoon into this. Log stuff is a _bit_ > interesting. When I wbinfo -i zbeeble, I get: > > [2016/07/11 01:10:37.408526, 1, pid=24476, effective(0, 0), real(0, 0)] > ../librpc/ndr/ndr.c:439(ndr_print_function_debu > g) > wbint_LookupName: struct wbint_LookupName > in: struct wbint_LookupName >...

folks, hi, after some quiet advice i've tracked down a method for compiling python2.5 using msvcr80 that _will_ actually work both under native win32 and also under wine, but it's a _bit_ dodgy, as i couldn't track down where you're supposed to put Microsoft.VC80.CRT, except in the path of the application where it's running from. so, instead, i put the _contents_ of Microsoft.VC80.CRT.manifest into the manifest for the file, and this _does_ actually seem to work. i'...