lkml.org 
[lkml]   [2015]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCHSET] printk, netconsole: implement reliable netconsole
From
Date
Tejun Heo wrote:
> On Sat, Apr 18, 2015 at 03:03:46AM +0900, Tetsuo Handa wrote:
> > packet will be sufficient for finding out whether the packets were lost and/or
> > reordered in flight.
> >
> > printk("Hello");
> > => netconsole sends "00000000 Hello" using UDP
> > printk("netconsole");
> > => netconsole sends "00000001 netconsole" using UDP
> > printk("world\n");
> > => netconsole sends "00000002 world\n" using UDP
> >
> > It might be nice to allow administrator to prefix a sequence number
> > to netconsole messages for those who are using special receiver
> > program (e.g. ncrx) which checks that sequence number.
>
> That said, this is pretty much what the first 12 patches do (except
> for the last printk patch, which can be taken out). We already have
> sequencing and established format to expose them to userland - try cat
> /dev/kmsg, which btw is what local loggers on modern systems use
> anyway. Why introduce netconsole's own version of metadata?

I didn't mean to introduce netconsole's own version of metadata.
I meant we don't need to implement in-kernel retry logic.

If we can assume that scheduler is working, adding a kernel thread that
does

while (1) {
read messages with metadata from /dev/kmsg
send them using UDP network
}

might be easier than modifying netconsole module.

>
> Thanks.
>
> --
> tejun
>


\
 
 \ /
  Last update: 2015-04-17 21:01    [W:0.069 / U:3.792 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site