mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -rt] scheduling while atomic in remove_proc_entry()
Date: Mon, 08 Jan 2007 04:59:37 -0800	[thread overview]
Message-ID: <1168261177.26086.284.camel@imap.mvista.com> (raw)
In-Reply-To: <1168258802.6235.18.camel@twins>

On Mon, 2007-01-08 at 13:20 +0100, Peter Zijlstra wrote:

> 
> Well, no. Draining after the inspect 'all' loop doesn't make sense, but
> looking at 2.6.20-rc3-rt0 remove_proc_entry() looks sane.

When it was inside the loop it drained every iteration . So it made more
sense to put it after the loop. But I don't have a clue what the drain
is doing (might be good to add liberal comments, if you haven't
already).

Daniel


      reply	other threads:[~2007-01-08 13:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-29 21:12 Daniel Walker
2007-01-08 12:20 ` Peter Zijlstra
2007-01-08 12:59   ` Daniel Walker [this message]

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=1168261177.26086.284.camel@imap.mvista.com \
    --to=dwalker@mvista.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®