On Thu, Jun 19, 2014 at 10:07 PM, H. Peter Anvin wrote:
>
> For each of those transfers, we don't free the source memory until the
> very end. We could free that memory as we process the input, requiring
> less total memory.
Yes, that would be nice enhancement.
Yinghai
--
To unsubscribe from th
On 06/19/2014 10:02 PM, Yinghai Lu wrote:
> On Thu, Jun 19, 2014 at 9:29 PM, H. Peter Anvin wrote:
>> On 06/19/2014 07:12 PM, Yinghai Lu wrote:
>>>
>>> Also need to use that in write_buffer path for cpio that have file is
>>> more than file.
>>
>> That sentence doesn't make sense.
>
> I mean this
On Thu, Jun 19, 2014 at 9:29 PM, H. Peter Anvin wrote:
> On 06/19/2014 07:12 PM, Yinghai Lu wrote:
>>
>> Also need to use that in write_buffer path for cpio that have file is
>> more than file.
>
> That sentence doesn't make sense.
I mean this path:
unpack_to_rootfs ===> write_buffer ===> act
On 06/19/2014 07:12 PM, Yinghai Lu wrote:
> When initrd (compressed or not) is used, kernel report data corrupted
> with /dev/ram0.
>
> The root cause:
> During initramfs checking, if it is initrd, it will be transferred to
> /initrd.image with sys_write.
> sys_write only support 2G-4K write, so i
4 matches
Mail list logo
