[CRIU] open files issue

[Sanidhya Kashyap]

On 12/17/2014 08:14 AM, Pavel Emelyanov wrote:
> On 12/15/2014 08:26 PM, Sanidhya Kashyap wrote:
>> Hello everyone,
>>
>> I have been using criu to checkpoint memcached which works quite well but there
>> is an issue with the dumping of the open files - func: dump_task_files_seized in
>> cr-dump.c, specially dump_one_file in files.c. 	
>>
>> The function dump_one_file actually takes malmost 99% of the time when doing
>> either single dump or multiple pre-dumps followed by a single dump. I have
>> attached the dump with this email.
> 
> How did you get these 99%? Have you used perf tool? If yes, can you show
> the full tree of calls?
> 

I did it on the basis of time and introduced basic time codes to get the info.
Actually, it was around 90%, not 99%. Sorry for the typo.



> Either you can move the memcached into net namespace, then network lock would
> happen extremely fast. Of you can batch the locking with iptables and do it
> directly with the kernel API or, at least, with the libnetfilter, not with the
> fork + exec.
> 

Yeah, I happen to figure it out before the reply. Currently, I am using libiptc
which works fine and has drastically decreased the time. Still have to write a
patch for the removal of the rules, will do it and send the relevant patch for
review.


Thanks,
Sanidhya