From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Cyrill Gorcunov <gorcunov@openvz.org>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH 3/3][RFC] x86: x2apic/cluster: Do not handle cpumask allocation errors
Date: Mon, 21 May 2012 17:19:18 -0700 [thread overview]
Message-ID: <1337645958.1997.172.camel@sbsiddha-desk.sc.intel.com> (raw)
In-Reply-To: <20120518102659.GC31517@dhcp-26-207.brq.redhat.com>
On Fri, 2012-05-18 at 12:26 +0200, Alexander Gordeev wrote:
> With this fix allocations of cpumasks are assumed always successfull
> and possible failures result in BUG().
BUG check for memory allocation failures in IPI path is not a good idea.
We will be using IPI's to flush TLB's before we evict the pages for
recovering from low-memory conditions. We need to provide a clean fall
back path.
So NAK.
thanks,
suresh
prev parent reply other threads:[~2012-05-22 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 10:26 Alexander Gordeev
2012-05-22 0:19 ` Suresh Siddha [this message]
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=1337645958.1997.172.camel@sbsiddha-desk.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=agordeev@redhat.com \
--cc=gorcunov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
--cc=yinghai@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®