On 03/25/2013 05:32 PM, Pavel Emelyanov wrote:
> On 03/11/2013 01:11 PM, Pavel Emelyanov wrote:
>> Hi.
>>
>> This v3 series is ported on v3.9-rc2 and patches' changelogs are fixed
>> according to Thomas' feedback to contain info why the change is required.
>
> Gentlemen,
>
> I'm sorry for botheri
On 03/11/2013 01:11 PM, Pavel Emelyanov wrote:
> Hi.
>
> Currently kernel doesn't provide any API for getting information about
> what timers are currently created by process and in which state they
> are. Also, the way timer IDs are generated makes it impossible to create
> a timer with any desi
On Fri, 8 Mar 2013, Pavel Emelyanov wrote:
> On 02/21/2013 10:21 PM, Pavel Emelyanov wrote:
> > Hi.
> >
> > Here's another approach to address the problems with insufficient API
> > of posix timers.
>
> Gentlemen,
Sir,
that caught my attention. Will move it up on my todo list :)
--
To unsubs
On 02/21/2013 10:21 PM, Pavel Emelyanov wrote:
> Hi.
>
> Here's another approach to address the problems with insufficient API
> of posix timers.
Gentlemen,
If you don't mind, I'd like to remind you about this set :) If you could
find some time in your schedule and share your thoughts about one
On 02/21/2013 05:21 AM, Matthew Helsley wrote:
> On Thu, Feb 14, 2013 at 8:18 AM, Pavel Emelyanov wrote:
>> Hi.
>>
>> I'm working on the checkpoint-restore project (http://criu.org), briefly
>> it's aim is to collect information about process' state and saving it so
>> that later it is possible to
On Thu, Feb 14, 2013 at 8:18 AM, Pavel Emelyanov wrote:
> Hi.
>
> I'm working on the checkpoint-restore project (http://criu.org), briefly
> it's aim is to collect information about process' state and saving it so
> that later it is possible to recreate the processes in the very same state
> as th
6 matches
Mail list logo
