From: Hugh Dickins <hugh@veritas.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Andrea Arcangeli <andrea@novell.com>,
Albert Cahalan <albert@users.sourceforge.net>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton OSDL <akpm@osdl.org>,
Albert Cahalan <albert@users.sourceforge.net>
Subject: Re: per-process shared information
Date: Fri, 15 Oct 2004 23:04:45 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0410152255290.7849-100000@localhost.localdomain> (raw)
In-Reply-To: <20041015214026.GR5607@holomorphy.com>
On Fri, 15 Oct 2004, William Lee Irwin III wrote:
> On Fri, Oct 15, 2004 at 11:28:31PM +0200, Andrea Arcangeli wrote:
> > Ok fine. But first it has to be included into mainline, then of course
> > we'll merge it. Fixing Oracle at the expense of being incompatible with
> > the user-ABI with future 2.6 is a no-way.
>
> The thing I wanted to convey most was that I got an acknowledgment from
> the original sources of Oracle's requirement, including the project
> lead for the team that maintains statistics collection kit that uses
> the statistics to estimate the client capacity of a system and not just
> whoever got the bug assigned to them inside Oracle, that Hugh's specific
> implementation we want to go with also satisfies the user requirements.
> They've even committed to runtime testing the patches to verify the
> patch does everything they want it to.
Andrea, Bill, great, thanks a lot for doing all the fieldwork on this.
After going through the discussions, I'm inclined to stick with the
patch as is i.e. "correct the 2.6 bug" in the "shared" third field of
/proc/pid/statm, rather than adding this as another field on the end.
Once 2.6.9 is out and we're open for patches again, I'll break it
into the four parts originally outlined, and send to Andrew.
Hugh
next prev parent reply other threads:[~2004-10-15 22:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 23:10 Andrea Arcangeli
2004-10-14 21:47 ` Marcelo Tosatti
2004-10-14 23:58 ` Andrea Arcangeli
2004-10-14 23:17 ` Marcelo Tosatti
2004-10-15 10:45 ` William Lee Irwin III
2004-10-14 21:49 ` Hugh Dickins
2004-10-14 22:11 ` William Lee Irwin III
2004-10-14 22:37 ` Andrea Arcangeli
2004-10-15 10:51 ` William Lee Irwin III
2004-10-15 11:56 ` Hugh Dickins
2004-10-15 13:19 ` Albert Cahalan
2004-10-15 14:28 ` William Lee Irwin III
2004-10-15 14:40 ` Albert Cahalan
2004-10-15 14:52 ` William Lee Irwin III
2004-10-15 17:02 ` Andrea Arcangeli
2004-10-15 16:20 ` Andrea Arcangeli
2004-10-15 16:31 ` Albert Cahalan
2004-10-15 17:10 ` William Lee Irwin III
2004-10-15 19:29 ` Albert Cahalan
2004-10-15 17:13 ` Andrea Arcangeli
2004-10-15 17:51 ` Albert Cahalan
2004-10-15 18:14 ` Andrea Arcangeli
2004-10-15 18:30 ` William Lee Irwin III
2004-10-15 18:40 ` Andrea Arcangeli
2004-10-15 18:47 ` William Lee Irwin III
2004-10-15 19:23 ` Andrea Arcangeli
2004-10-15 20:41 ` William Lee Irwin III
2004-10-15 20:52 ` Andrea Arcangeli
2004-10-15 21:16 ` William Lee Irwin III
2004-10-15 21:28 ` Andrea Arcangeli
2004-10-15 21:40 ` William Lee Irwin III
2004-10-15 22:04 ` Hugh Dickins [this message]
2004-10-19 15:09 ` Bill Davidsen
2004-10-15 16:04 ` Andrea Arcangeli
2004-10-19 15:18 ` Bill Davidsen
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=Pine.LNX.4.44.0410152255290.7849-100000@localhost.localdomain \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=albert@users.sourceforge.net \
--cc=andrea@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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®