cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [DLM] Fix up memory alloc/kmap
Date: Thu, 13 Nov 2008 11:29:33 -0600	[thread overview]
Message-ID: <20081113172933.GA13163@redhat.com> (raw)
In-Reply-To: <1226570178.3525.23.camel@localhost.localdomain>

On Thu, Nov 13, 2008 at 09:56:18AM +0000, Steven Whitehouse wrote:
> It is left as an exercise for the reader to consider whether its a bug
> that DLM isn't using highmem pages for its internal buffers (in which
> case we'd have to solve the allocation problem at kmap time), or whether
> its a bug that the kmap/kunmap pairs are there at all (and can thus be
> removed, which is the simpler solution) :-)

Thanks, I'll remove all the kmap/kunmap calls, then.



      reply	other threads:[~2008-11-13 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 15:05 [Cluster-devel] [DLM] Fix up memory alloc/kmap Steven Whitehouse
2008-11-11 11:02 ` Steven Whitehouse
2008-11-12 23:14   ` [Cluster-devel] " David Teigland
2008-11-13  9:56     ` Steven Whitehouse
2008-11-13 17:29       ` David Teigland [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=20081113172933.GA13163@redhat.com \
    --to=teigland@redhat.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).