From: Andrea Arcangeli <aarcange@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: linux-mm@kvack.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
akpm@linux-foundation.org, hannes@cmpxchg.org
Subject: Re: [PATCH 6/8] mm: Make transparent huge code not depend upon the details of pgtable_t
Date: Wed, 3 Oct 2012 00:49:21 +0200 [thread overview]
Message-ID: <20121002224921.GR4763@redhat.com> (raw)
In-Reply-To: <20121002.182718.250164928532772411.davem@davemloft.net>
Hi Dave,
On Tue, Oct 02, 2012 at 06:27:18PM -0400, David Miller wrote:
>
> The code currently assumes that pgtable_t is a struct page pointer.
>
> Fix this by pushing pgtable management behind arch helper functions.
This should be fixed in -mm already, it's from the s390x support.
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Arcangeli <aarcange@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: linux-mm@kvack.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
akpm@linux-foundation.org, hannes@cmpxchg.org
Subject: Re: [PATCH 6/8] mm: Make transparent huge code not depend upon the details of pgtable_t
Date: Tue, 02 Oct 2012 22:49:21 +0000 [thread overview]
Message-ID: <20121002224921.GR4763@redhat.com> (raw)
In-Reply-To: <20121002.182718.250164928532772411.davem@davemloft.net>
Hi Dave,
On Tue, Oct 02, 2012 at 06:27:18PM -0400, David Miller wrote:
>
> The code currently assumes that pgtable_t is a struct page pointer.
>
> Fix this by pushing pgtable management behind arch helper functions.
This should be fixed in -mm already, it's from the s390x support.
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Arcangeli <aarcange@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: linux-mm@kvack.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
akpm@linux-foundation.org, hannes@cmpxchg.org
Subject: Re: [PATCH 6/8] mm: Make transparent huge code not depend upon the details of pgtable_t
Date: Wed, 3 Oct 2012 00:49:21 +0200 [thread overview]
Message-ID: <20121002224921.GR4763@redhat.com> (raw)
In-Reply-To: <20121002.182718.250164928532772411.davem@davemloft.net>
Hi Dave,
On Tue, Oct 02, 2012 at 06:27:18PM -0400, David Miller wrote:
>
> The code currently assumes that pgtable_t is a struct page pointer.
>
> Fix this by pushing pgtable management behind arch helper functions.
This should be fixed in -mm already, it's from the s390x support.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-10-02 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 22:27 [PATCH 6/8] mm: Make transparent huge code not depend upon the details of pgtable_t David Miller
2012-10-02 22:27 ` David Miller
2012-10-02 22:27 ` David Miller
2012-10-02 22:49 ` Andrea Arcangeli [this message]
2012-10-02 22:49 ` Andrea Arcangeli
2012-10-02 22:49 ` Andrea Arcangeli
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=20121002224921.GR4763@redhat.com \
--to=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hannes@cmpxchg.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sparclinux@vger.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 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.