From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
benh@kernel.crashing.org, paulus@samba.org,
Balbir Singh <bsingharora@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V2 1/2] powerpc/mm/slice: Move slice_mask struct definition to slice.c
Date: Tue, 14 Feb 2017 12:08:32 +0530 [thread overview]
Message-ID: <89a807a3-289c-3cca-dc52-930c6d7f4021@linux.vnet.ibm.com> (raw)
In-Reply-To: <87mvdpmgpi.fsf@concordia.ellerman.id.au>
On Tuesday 14 February 2017 11:55 AM, Michael Ellerman wrote:
> "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> writes:
>
>> diff --git a/arch/powerpc/mm/slice.c b/arch/powerpc/mm/slice.c
>> index b3f45e413a60..08ac27eae408 100644
>> --- a/arch/powerpc/mm/slice.c
>> +++ b/arch/powerpc/mm/slice.c
>> @@ -37,7 +37,16 @@
>> #include <asm/hugetlb.h>
>>
>> static DEFINE_SPINLOCK(slice_convert_lock);
>> -
>> +/*
>> + * One bit per slice. We have lower slices which cover 256MB segments
>> + * upto 4G range. That gets us 16 low slices. For the rest we track slices
>> + * in 1TB size.
> Can we tighten this comment up a bit.
>
> What about:
>
>> + * One bit per slice. The low slices cover the range 0 - 4GB, each
>> * slice being 256MB in size, for 16 low slices. The high slices
>> * cover the rest of the address space at 1TB granularity, with the
>> * exception of high slice 0 which covers the range 4GB - 1TB.
> OK?
good.
>
>> + * 64 below is actually SLICE_NUM_HIGH to fixup complie errros
> That line is bogus AFAICS, it refers to the old hardcoded value (prior
> to 512), I'll drop it.
Thanks
-aneesh
prev parent reply other threads:[~2017-02-14 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 12:24 [PATCH V2 1/2] powerpc/mm/slice: Move slice_mask struct definition to slice.c Aneesh Kumar K.V
2017-02-13 12:24 ` [PATCH V2 2/2] powerpc/mm/slice: Update slice mask printing to use bitmap printing Aneesh Kumar K.V
2017-02-14 6:25 ` [PATCH V2 1/2] powerpc/mm/slice: Move slice_mask struct definition to slice.c Michael Ellerman
2017-02-14 6:38 ` Aneesh Kumar K.V [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=89a807a3-289c-3cca-dc52-930c6d7f4021@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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 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).