[lkml]   [2015]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCHSET] printk, netconsole: implement reliable netconsole
Tejun Heo wrote:
> * Implement netconsole retransmission support. Matching rx socket on
> the source port is automatically created for extended targets and
> the log receiver can request retransmission by sending reponse
> packets. This is completely decoupled from the main write path and
> doesn't make netconsole less robust when things start go south.

If the sender side can wait for retransmission, why can't we use
userspace programs (e.g. rsyslogd)?

For me, netconsole is mainly for saving kernel messages which cannot be
waited for a few deciseconds (e.g. system reset by softdog's timeout) and
for saving kernel messages (e.g. SysRq-t) during disk I/O hang up.
I have a logger for receiving netconsole messages at
and things I expect for netconsole are shown below.

(a) spool the message to send up to "1 line" or "adimn configured size"
so that total number of small UDP packets can be reduced

(b) don't hesitate to send the spooled message immediately if either
kernel panic or system reset is in progress

(c) allow different console log level for different console drivers
so that I can send kernel messages via netconsole without making
local console noisy

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