From: Chaitanya Lala <clala@riverbed.com>
To: Corey Minyard <minyard@acm.org>
Cc: Chaitanya Lala <Chaitanya.Lala@riverbed.com>,
"martin.wilck@ts.fujitsu.com" <martin.wilck@ts.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Regarding patchwork patch #28003
Date: Thu, 11 Jun 2009 12:02:48 -0700 [thread overview]
Message-ID: <4A3154D8.10807@riverbed.com> (raw)
In-Reply-To: <4A314526.5030704@acm.org>
Corey Minyard wrote:
> Chaitanya Lala wrote:
>
>> Hi,
>> I have been facing the issue of the kipmid's CPU usage spiking since a long time.
>> I have tested the patch sent by Martin (limit CPU time spent in kipmid (version 4)) and it solves the issue for me.
>> I do not see any activity/feedback on the patch.
>> Can I help in some-way to ensure that this patch is merged ?
>>
>>
> I will add this to the patchset I put out for 2.6.30, and if that goes
> well it will go into the mainstream kernel.
>
Thanks for the response. Will look forward to it.
Thanks,
Chaitanya
> -corey
>
next prev parent reply other threads:[~2009-06-11 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 17:33 Regarding patchwork patch #28003 Chaitanya Lala
2009-06-11 17:55 ` Corey Minyard
2009-06-11 19:02 ` Chaitanya Lala [this message]
2009-06-15 8:41 ` Martin Wilck
2009-06-15 14:32 ` Corey Minyard
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=4A3154D8.10807@riverbed.com \
--to=clala@riverbed.com \
--cc=Chaitanya.Lala@riverbed.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.wilck@ts.fujitsu.com \
--cc=minyard@acm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.