public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Haoqiang Zheng <haoqiang@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] swap-sched: schedule with dynamic dependency detection (2.6.12-rc3)
Date: Mon, 9 May 2005 09:26:55 +1000	[thread overview]
Message-ID: <200505090926.59335.kernel@kolivas.org> (raw)
In-Reply-To: <d6e6e6dd05050808556d83feb7@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

On Mon, 9 May 2005 01:55, Haoqiang Zheng wrote:
> I am not quite sure about what do you mean for " a ring of dependent
> tasks".  Do you mean the situation that A depends on B while at the
> same time B depends on A?  It shouldn't happen since in swap-sched,
> the dependency is generated on the fly. Task A depends on B only when
> A blocks on waiting for B. For example, if task A blocks on
> "read(pipe_fd,...)" and B is the task that can do
> "write(pipe_fd,...)", then A is depending on B.  Once A is waked up,
>  A no longer depends on any other task. So the "ring of dependent
> tasks" shouldn't happen, otherwise it's a deadlock.

Ok so how does it respond to process_load in contest?

Cheers,
Con

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-05-08 23:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-08  6:11 [RFC PATCH] swap-sched: schedule with dynamic dependency detection (2.6.12-rc3) Haoqiang Zheng
2005-05-08  7:33 ` Con Kolivas
2005-05-08 15:55   ` Haoqiang Zheng
2005-05-08 23:26     ` Con Kolivas [this message]
2005-05-09  3:56       ` Haoqiang Zheng
2005-05-09  5:57         ` Con Kolivas
2005-05-11  4:23           ` Haoqiang Zheng
2005-05-08  7:46 ` Lee Revell
2005-05-10  8:22 ` Coywolf Qi Hunt

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=200505090926.59335.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=haoqiang@gmail.com \
    --cc=linux-kernel@vger.kernel.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