On Thu, May 02, 2019 at 04:20:03PM -0700, Dan Williams wrote:
> On Thu, May 2, 2019 at 3:46 PM Pavel Tatashin
> wrote:
> >
> > Hi Dan,
> >
> > How do you test these patches? Do you have any instructions?
>
> Yes, I briefly mentioned this in the cover letter, but here is the
> test I am using:
>
On Thu, May 2, 2019 at 3:46 PM Pavel Tatashin wrote:
>
> Hi Dan,
>
> How do you test these patches? Do you have any instructions?
Yes, I briefly mentioned this in the cover letter, but here is the
test I am using:
>
> I see for example that check_hotplug_memory_range() still enforces
>
On Thu, May 2, 2019 at 4:20 PM Dan Williams wrote:
>
> On Thu, May 2, 2019 at 3:46 PM Pavel Tatashin
> wrote:
> >
> > Hi Dan,
> >
> > How do you test these patches? Do you have any instructions?
>
> Yes, I briefly mentioned this in the cover letter, but here is the
> test I am using:
Sorry,
Hi Dan,
How do you test these patches? Do you have any instructions?
I see for example that check_hotplug_memory_range() still enforces
memory_block_size_bytes() alignment.
Also, after removing check_hotplug_memory_range(), I tried to online
16M aligned DAX memory, and got the following panic:
I am also taking a look at this work now. I will review and test it in
the next couple of days.
Pasha
On Tue, Apr 23, 2019 at 9:17 AM Oscar Salvador wrote:
>
> On Wed, 2019-04-17 at 15:59 -0700, Dan Williams wrote:
> > On Wed, Apr 17, 2019 at 3:04 PM Andrew Morton > org> wrote:
> > >
> > > On
On Wed, 2019-04-17 at 15:59 -0700, Dan Williams wrote:
> On Wed, Apr 17, 2019 at 3:04 PM Andrew Morton org> wrote:
> >
> > On Wed, 17 Apr 2019 11:38:55 -0700 Dan Williams > el.com> wrote:
> >
> > > The memory hotplug section is an arbitrary / convenient unit for
> > > memory
> > > hotplug.
On Thu, Apr 18, 2019 at 5:45 AM Jeff Moyer wrote:
[..]
> >> > v6 and we're not showing any review activity. Who would be suitable
> >> > people to help out here?
> >>
> >> There was quite a bit of review of the cover letter from Michal and
> >> David, but you're right the details not so much as
Dan Williams writes:
>> On Wed, Apr 17, 2019 at 3:59 PM Dan Williams
>> wrote:
>>
>> On Wed, Apr 17, 2019 at 3:04 PM Andrew Morton
>> wrote:
>> >
>> > On Wed, 17 Apr 2019 11:38:55 -0700 Dan Williams
>> > wrote:
>> >
>> > > The memory hotplug section is an arbitrary / convenient unit for
On Wed, Apr 17, 2019 at 3:59 PM Dan Williams wrote:
>
> On Wed, Apr 17, 2019 at 3:04 PM Andrew Morton
> wrote:
> >
> > On Wed, 17 Apr 2019 11:38:55 -0700 Dan Williams
> > wrote:
> >
> > > The memory hotplug section is an arbitrary / convenient unit for memory
> > > hotplug. 'Section-size'
On Wed, Apr 17, 2019 at 3:04 PM Andrew Morton wrote:
>
> On Wed, 17 Apr 2019 11:38:55 -0700 Dan Williams
> wrote:
>
> > The memory hotplug section is an arbitrary / convenient unit for memory
> > hotplug. 'Section-size' units have bled into the user interface
> > ('memblock' sysfs) and can not
On Wed, 17 Apr 2019 11:38:55 -0700 Dan Williams
wrote:
> The memory hotplug section is an arbitrary / convenient unit for memory
> hotplug. 'Section-size' units have bled into the user interface
> ('memblock' sysfs) and can not be changed without breaking existing
> userspace. The section-size
Changes since v5 [1]:
- Rebase on next-20190416 and the new 'struct mhp_restrictions'
infrastructure.
- Extend mhp_restrictions to the 'remove' case so the sub-section policy
can be clarified with respect to the memblock-api in a symmetric
manner with the 'add' case.
- Kill is_dev_zone()
12 matches
Mail list logo
