From: Steven Rostedt <rostedt@goodmis.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
kus Kusche Klaus <kus@keba.com>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: Why yield in coredump_wait? [was: Re: Resent: BUG in RT 45-01 when RT program dumps core]
Date: Thu, 19 May 2005 12:03:24 -0400 [thread overview]
Message-ID: <1116518604.27471.15.camel@localhost.localdomain> (raw)
In-Reply-To: <1116517651.21685.50.camel@mindpipe>
On Thu, 2005-05-19 at 11:47 -0400, Lee Revell wrote:
> On Thu, 2005-05-19 at 09:37 -0400, Steven Rostedt wrote:
> > Now if there were no other threads to wait on it would just continue.
> > So, is there some real reason that this yield is there? Or is it just
> > trying to be nice, as in saying, "I'm dieing now and just don't want to
> > waste others time" (which I highly doubt is the case).
>
> Why do you highly doubt this is the case? This is actually the behavior
> I would expect.
Because yield just doesn't cut it. Yeah, OK it stops its time slice at
that moment, but it will still come in and preempt whoever to finish the
job. If it really wanted to do the "I'm dieing let others run" then it
should change its priority or nice value.
-- Steve
next prev parent reply other threads:[~2005-05-19 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:36 Resent: BUG in RT 45-01 when RT program dumps core kus Kusche Klaus
2005-05-19 11:56 ` Steven Rostedt
2005-05-19 12:38 ` Serge Noiraud
2005-05-19 13:12 ` Steven Rostedt
2005-05-19 13:37 ` Why yield in coredump_wait? [was: Re: Resent: BUG in RT 45-01 when RT program dumps core] Steven Rostedt
2005-05-19 15:47 ` Lee Revell
2005-05-19 16:03 ` Steven Rostedt [this message]
2005-05-19 17:25 ` Daniel Walker
2005-05-19 17:43 ` Alan Cox
2005-05-19 18:05 ` Steven Rostedt
2005-05-23 7:53 ` Ingo Molnar
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=1116518604.27471.15.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=kus@keba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--cc=torvalds@osdl.org \
/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
all inboxes | Powered by JetHome®