From: Tomasz Figa <tomasz.figa@gmail.com>
To: Subash Patel <subashrp@gmail.com>
Cc: Olof Johansson <olof@lixom.net>,
linux-samsung-soc@vger.kernel.org,
Kukjin Kim <kgene.kim@samsung.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: fix split memory bank for SSDK5440
Date: Fri, 21 Dec 2012 00:18:39 +0100 [thread overview]
Message-ID: <3158118.uctD3XVWRG@flatron> (raw)
In-Reply-To: <50D38F04.8020307@gmail.com>
Hi Subash,
On Thursday 20 of December 2012 14:19:48 Subash Patel wrote:
> I would like to ask a question here. Do we need to have sparse even if
> the physical memory is contiguous? All the recent exynos machines come
> with physical banks without any holes, and I am thinking why not drop it
> and use flat mem instead. With LPAE these sections sizes wont be useful,
> and I dont like to keep different section sizes for different
> configurations. Any suggestions/opinions are very much helpful to me.
Since sparse memory is the only option available on Exynos currently in
kernel configuration, I assume there was a reason for it. However I am not
an expert in memory management, so please correct me if I am wrong.
Best regards,
Tomasz Figa
WARNING: multiple messages have this Message-ID (diff)
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: fix split memory bank for SSDK5440
Date: Fri, 21 Dec 2012 00:18:39 +0100 [thread overview]
Message-ID: <3158118.uctD3XVWRG@flatron> (raw)
In-Reply-To: <50D38F04.8020307@gmail.com>
Hi Subash,
On Thursday 20 of December 2012 14:19:48 Subash Patel wrote:
> I would like to ask a question here. Do we need to have sparse even if
> the physical memory is contiguous? All the recent exynos machines come
> with physical banks without any holes, and I am thinking why not drop it
> and use flat mem instead. With LPAE these sections sizes wont be useful,
> and I dont like to keep different section sizes for different
> configurations. Any suggestions/opinions are very much helpful to me.
Since sparse memory is the only option available on Exynos currently in
kernel configuration, I assume there was a reason for it. However I am not
an expert in memory management, so please correct me if I am wrong.
Best regards,
Tomasz Figa
next prev parent reply other threads:[~2012-12-20 23:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 19:03 [PATCH] ARM: dts: fix split memory bank for SSDK5440 Kukjin Kim
2012-12-20 19:03 ` Kukjin Kim
2012-12-20 19:56 ` Olof Johansson
2012-12-20 19:56 ` Olof Johansson
2012-12-20 21:14 ` Tomasz Figa
2012-12-20 21:14 ` Tomasz Figa
2012-12-20 22:19 ` Subash Patel
2012-12-20 22:19 ` Subash Patel
2012-12-20 23:18 ` Tomasz Figa [this message]
2012-12-20 23:18 ` Tomasz Figa
2012-12-21 0:43 ` Kukjin Kim
2012-12-21 0:43 ` Kukjin Kim
2012-12-20 23:41 ` Russell King - ARM Linux
2012-12-20 23:41 ` Russell King - ARM Linux
2012-12-21 0:32 ` Kukjin Kim
2012-12-21 0:32 ` Kukjin Kim
2012-12-21 0:35 ` Olof Johansson
2012-12-21 0:35 ` Olof Johansson
2012-12-21 0:56 ` Cho KyongHo
2012-12-21 0:56 ` Cho KyongHo
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=3158118.uctD3XVWRG@flatron \
--to=tomasz.figa@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=subashrp@gmail.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 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.