From: Peter Williams <pwil3058@bigpond.net.au>
To: Erik Jacobson <erikj@subway.americas.sgi.com>
Cc: linux-kernel@vger.kernel.org, jlan@engr.sgi.com, limin@engr.sgi.com
Subject: Re: [PATCH] Process Aggregates (PAGG) for 2.6.7
Date: Fri, 25 Jun 2004 09:22:31 +1000 [thread overview]
Message-ID: <40DB6237.2050704@bigpond.net.au> (raw)
In-Reply-To: <Pine.SGI.4.53.0406241239400.340142@subway.americas.sgi.com>
Erik Jacobson wrote:
> Attached is a PAGG patch to kernel 2.6.7.
>
> The maintainers of two patches that make use of PAGG will post their patches
> in to this discussion thread shortly.
>
> The biggest change in this patch from the last one I posted is that
> Peter Williams supplied an implementation for the init function pointer
> in the pagg hook. We kicked this around a few times to flush out
> locking issues.
I wish that you had included me in this discussion. Can you explain
exactly what the locking issues with my code were? We might have been
able to come up with a better solution than the one you have used which
places unnecessary restrictions (i.e. no blocking) on the init()
callbacks which weren't applicable in the code that I provided. Since
these callbacks are highly likely to want to allocate dynamic memory
there is always a chance that they will block and the no blocking
restriction becomes an unnecessary burden.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2004-06-24 23:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 18:08 Erik Jacobson
2004-06-24 18:32 ` Limin Gu
2004-06-24 18:57 ` Chris Wright
2004-06-24 19:12 ` Limin Gu
2004-06-24 19:15 ` Chris Wright
2004-06-24 19:31 ` Jay Lan
2004-06-24 23:22 ` Peter Williams [this message]
2004-06-25 2:02 ` Erik Jacobson
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=40DB6237.2050704@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=erikj@subway.americas.sgi.com \
--cc=jlan@engr.sgi.com \
--cc=limin@engr.sgi.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
all inboxes | Powered by JetHome®