Hello,
On Fri, Feb 26, 2016 at 03:47:18PM +0100, Petr Mladek wrote:
> > Could you explain in more detail what did you mean by IPC problems?
>
> I guess that the idea was to make IPC more effective in general.
> You definitely could not move all functionality that needs IPC
> into the kernel.
1.
On Fri 2016-02-26 14:22:42, Kazimierz Krosman wrote:
> On 02/25/2016 10:47 PM, Tejun Heo wrote:
> >I'm not sure this is the right layer to implement generic logging
> >facility.
> In general this patches add only one feature- possibility of adding
> and deleting
> new kmsg devices, so I think that
On 02/25/2016 10:47 PM, Tejun Heo wrote:
I'm not sure this is the right layer to implement generic logging
facility.
In general this patches add only one feature- possibility of adding and
deleting
new kmsg devices, so I think that it can be treated as kmsg upgrade.
2. Using kmsg can cause low
Hello, Kazimierz.
On Wed, Feb 24, 2016 at 12:53:13PM +0100, Kazimierz Krosman wrote:
> 1. kmsg device does not require maintenance by reader process side.
> Multiple writers can write to a device and new records overwrite logs saved
> earlier.
> When system crashes logs can be restored with pstor
Dear All,
This is the sixth iteration of Marcin Niesluchowski's series of patches
extending kmsg interface with ability to dynamically create (and destroy)
kmsg-like devices which can be used by userspace for logging,
Changed from v5:
* ioctl that adds kmsg device with minor number higher than
