linux-um archives
 help / color / mirror / Atom feed
From: Werner Almesberger <werner@almesberger.net>
To: Adam Heath <adam@sonycom.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] RFC: lossless printk
Date: Thu, 1 Apr 2004 08:30:25 -0300	[thread overview]
Message-ID: <20040401083025.Z28573@almesberger.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0404010149580.13832@gradall.private.brainfood.com>; from adam@doogie.org on Thu, Apr 01, 2004 at 01:53:58AM -0600

Adam Heath wrote:
> Don't define functions inline like that, place it in a header.

Of course. I just didn't want to touch yet another file for
now. After all, that's just a first try to get feedback.

> The code shouldn't retry forever.  If the output is blocked for a long time,
> the kernel will become stalled.

Hmm, that's a tricky one. What's a good policy in this case ?
Wait up to a fixed amount of time before continuing, and perhaps
do the same thing on the next printk ? Stop retrying after one
timeout ? Make all this configurable ?

> You also don't handle EINTR.

Good point. I actually never saw one happen, even though I have
workloads that almost only printk.

> Are you converting errno to a list of hashes?

Yeah :-) I'll fix this. You hit it usually for EPIPE or the
like.

> And couldn't writing to stderr
> have the same non-blocking problems?

Potentially yes. Not sure if it makes sense to try very hard
to get that last message out, though.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina     werner@almesberger.net /
/_http://www.almesberger.net/____________________________________________/


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2004-04-01 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01  7:25 [uml-devel] RFC: lossless printk Werner Almesberger
2004-04-01 10:58 ` Henrik Nordstrom
2004-04-01 15:36   ` Werner Almesberger
2004-04-01 17:42     ` Henrik Nordstrom
2004-04-01 18:28       ` Werner Almesberger
2004-04-01 20:36         ` Henrik Nordstrom
     [not found] ` <Pine.LNX.4.58.0404010149580.13832@gradall.private.brainfood.com>
2004-04-01 11:30   ` Werner Almesberger [this message]
2004-04-01 11:48     ` Henrik Nordstrom
2004-04-02 20:19       ` Werner Almesberger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040401083025.Z28573@almesberger.net \
    --to=werner@almesberger.net \
    --cc=adam@sonycom.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox