qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [PATCH v2 05/10] Optimize the function of packet_new


From: Rao, Lei
Subject: RE: [PATCH v2 05/10] Optimize the function of packet_new
Date: Fri, 12 Mar 2021 11:50:04 +0000

Oh, I understand what you mean, and will change it in V3.

Thanks,
Lei.

-----Original Message-----
From: lizhijian@fujitsu.com <lizhijian@fujitsu.com> 
Sent: Friday, March 12, 2021 6:23 PM
To: Rao, Lei <lei.rao@intel.com>; Zhang, Chen <chen.zhang@intel.com>; 
jasowang@redhat.com; quintela@redhat.com; dgilbert@redhat.com; 
pbonzini@redhat.com; lukasstraub2@web.de
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 05/10] Optimize the function of packet_new



> +            offset = colo_bitmap_find_dirty(ram_state, block, offset, 
> + &num);
IIUC, this return value would pass to the next round as start index,  so you 
should skip the already checked one.


Thanks


On 3/12/21 5:56 PM, Rao, Lei wrote:
> How about redefine a function named packet_new_nocopy?
> In comments, we can tell the caller don't release the buffer and the 
> packet_destroy will release it.
>
> Thanks,
> Lei.
> -----Original Message-----
> From:lizhijian@fujitsu.com  <lizhijian@fujitsu.com>
> Sent: Friday, March 12, 2021 2:53 PM
> To: Rao, Lei<lei.rao@intel.com>; Zhang, 
> Chen<chen.zhang@intel.com>;jasowang@redhat.com;quintela@redhat.com;dgi
> lbert@redhat.com;pbonzini@redhat.com;lukasstraub2@web.de
> Cc:qemu-devel@nongnu.org
> Subject: Re: [PATCH v2 05/10] Optimize the function of packet_new
>
>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]