From: Andrea Righi <righiandr@users.sourceforge.net>
To: Shailabh Nagar <nagar@watson.ibm.com>
Cc: Mark Seger <Mark.Seger@hp.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Jes Sorensen <jes@sgi.com>, Chris Sturtivant <csturtiv@sgi.com>,
Tony Ernst <tee@sgi.com>, LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: [PATCH] distinct tgid/tid I/O statistics (was: taskstats and /proc/.../io asymmetry?)
Date: Mon, 19 May 2008 18:36:19 +0200 [thread overview]
Message-ID: <4831AC83.7050908@users.sourceforge.net> (raw)
In-Reply-To: <482DF0C0.6050208@users.sourceforge.net>
Andrea Righi wrote:
> Patch against 2.6.25.4, tested in KVM.
Tested in latest linux-next (next-20080519) as well.
-Andrea
parent reply other threads:[~2008-05-19 16:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <482DF0C0.6050208@users.sourceforge.net>]
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=4831AC83.7050908@users.sourceforge.net \
--to=righiandr@users.sourceforge.net \
--cc=Mark.Seger@hp.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=csturtiv@sgi.com \
--cc=jes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nagar@watson.ibm.com \
--cc=tee@sgi.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;
as well as URLs for NNTP newsgroup(s).