From: Roland Dreier <rdreier@cisco.com>
To: Alexander Schmidt <alexs@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, ewg@lists.openfabrics.org,
linuxppc-dev@ozlabs.org, raisch@de.ibm.com,
Hoang-Nam Nguyen <HNGUYEN@linux.vnet.ibm.com>
Subject: Re: [ewg] Re: [PATCH 2.6.31] ehca: Tolerate dynamic memory operations and huge pages
Date: Tue, 16 Jun 2009 09:10:39 -0700 [thread overview]
Message-ID: <adazlc8w45c.fsf@cisco.com> (raw)
In-Reply-To: <20090616090809.34d162fc@BL3D1974.boeblingen.de.ibm.com> (Alexander Schmidt's message of "Tue, 16 Jun 2009 09:08:09 +0200")
> Yeah, the notifier code remains untouched as we still do not allow dynamic
> memory operations _while_ our module is loaded. The patch allows the driver to
> cope with DMEM operations that happened before the module was loaded, which
> might result in a non-contiguous memory layout. When the driver registers
> its global memory region in the system, the memory layout must be considered.
>
> We chose the term "toleration" instead of "support" to illustrate this.
I see. So things just silently broke in some cases when the driver was
loaded after operations you didn't tolerate?
Anyway, thanks for the explanation.
next prev parent reply other threads:[~2009-06-16 16:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 13:59 [PATCH 2.6.31] ehca: Tolerate dynamic memory operations and huge pages Hannes Hering
2009-06-10 0:02 ` Michael Ellerman
2009-06-10 8:54 ` Hannes Hering
2009-06-13 4:50 ` Roland Dreier
2009-06-16 7:08 ` Alexander Schmidt
2009-06-16 16:10 ` Roland Dreier [this message]
2009-06-17 6:41 ` [ewg] " Alexander Schmidt
2009-06-16 7:10 ` [PATCH 2.6.31 try 2] " Alexander Schmidt
2009-06-23 5:19 ` [ewg] " Roland Dreier
2009-06-23 8:11 ` Alexander Schmidt
2009-06-23 17:30 ` Roland Dreier
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=adazlc8w45c.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=HNGUYEN@linux.vnet.ibm.com \
--cc=alexs@linux.vnet.ibm.com \
--cc=ewg@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=raisch@de.ibm.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