All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuri Tikhonov <yur@emcraft.com>
To: "prodyut hazarika" <prodyuth@gmail.com>
Cc: wd@denx.de, yanok@emcraft.com, miltonm@bga.com,
	linuxppc-dev@ozlabs.org, paulus@samba.org, hugh@veritas.com,
	akpm@linux-foundation.org, dzu@denx.de
Subject: Re[2]: [PATCH][v3] powerpc 44x: support for 256KB PAGE_SIZE
Date: Tue, 13 Jan 2009 00:52:08 +0300	[thread overview]
Message-ID: <1473903899.20090113005208@emcraft.com> (raw)
In-Reply-To: <49c0ff980901121102t46b1e50cna6fbd333142485b7@mail.gmail.com>

=0D=0AHello Prodyut,

On Monday, January 12, 2009 you wrote:

> On Sun, Jan 11, 2009 at 10:42 AM, Yuri Tikhonov <yur@emcraft.com> wrote:
>>
>> This patch adds support for 256KB pages on ppc44x-based boards.
>>

> Hi Yuri,
> Do you still need the mm/shmem.c patch to avoid division by zero?

 Yes.

> I looked at the mm/shmem.c latest git code, and I see that it doesn't
> have the needed patch for 256KB page.

 Right. We proposed the work-around for this (which just simply=20
increased the sizes of variables which hold the overflowed values) to=20
LKML here:

http://lkml.org/lkml/2008/12/19/20

 If I understand Hugh right, then such a fix is acceptable, but much=20
far from the best, so Hugh is about to implement the correct fix for=20
the problem as soon as he'll find some time (big thanks to him for=20
this).

> I think another option would be to make 256KB compile only if CONFIG_SHME=
M=3Dn

 Agree. For the current situation it seems the better solution. I'll=20
update, and re-post the patch shortly.

 Regards, Yuri

 --
 Yuri Tikhonov, Senior Software Engineer
 Emcraft Systems, www.emcraft.com

      reply	other threads:[~2009-01-12 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11 18:42 [PATCH][v3] powerpc 44x: support for 256KB PAGE_SIZE Yuri Tikhonov
2009-01-12  0:53 ` Josh Boyer
2009-01-12 19:02 ` prodyut hazarika
2009-01-12 21:52   ` Yuri Tikhonov [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=1473903899.20090113005208@emcraft.com \
    --to=yur@emcraft.com \
    --cc=akpm@linux-foundation.org \
    --cc=dzu@denx.de \
    --cc=hugh@veritas.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=miltonm@bga.com \
    --cc=paulus@samba.org \
    --cc=prodyuth@gmail.com \
    --cc=wd@denx.de \
    --cc=yanok@emcraft.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.