From: Jeff Moyer <jmoyer@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "Dan Williams" <dan.j.williams@intel.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Logan Gunthorpe" <logang@deltatee.com>,
"Toshi Kani" <toshi.kani@hpe.com>,
"Vlastimil Babka" <vbabka@suse.cz>,
stable <stable@vger.kernel.org>, "Linux MM" <linux-mm@kvack.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 00/10] mm: Sub-section memory hotplug support
Date: Mon, 25 Mar 2019 10:28:00 -0400 [thread overview]
Message-ID: <x494l7rdo5r.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20190325101945.GD9924@dhcp22.suse.cz> (Michal Hocko's message of "Mon, 25 Mar 2019 11:19:45 +0100")
Michal Hocko <mhocko@kernel.org> writes:
>> > and I would like to know that you are
>> > not just shifting the problem to a smaller unit and a new/creative HW
>> > will force us to go even more complicated.
>>
>> HW will not do this to us. It's software that has the problem.
>> Namespace creation is unnecessarily constrained to 128MB alignment.
>
> And why is that a problem? A lack of documentation that this is a
> requirement? Something will not work with a larger alignment? Someting
> else?
See this email for one user-visible problem:
https://lore.kernel.org/lkml/x49imxbx22d.fsf@segfault.boston.devel.redhat.com/
Cheers,
Jeff
next prev parent reply other threads:[~2019-03-25 14:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 16:57 [PATCH v5 00/10] mm: Sub-section memory hotplug support Dan Williams
2019-03-22 16:58 ` [PATCH v5 09/10] libnvdimm/pfn: Fix fsdax-mode namespace info-block zero-fields Dan Williams
2019-03-22 18:05 ` [PATCH v5 00/10] mm: Sub-section memory hotplug support Michal Hocko
2019-03-22 18:32 ` Dan Williams
2019-03-25 10:19 ` Michal Hocko
2019-03-25 14:28 ` Jeff Moyer [this message]
2019-03-25 14:50 ` Michal Hocko
2019-03-25 20:03 ` Dan Williams
2019-03-26 8:04 ` Michal Hocko
2019-03-27 0:20 ` Dan Williams
2019-03-27 16:13 ` Michal Hocko
2019-03-27 16:17 ` Dan Williams
2019-03-28 13:38 ` David Hildenbrand
2019-03-28 14:16 ` Michal Hocko
2019-04-01 9:18 ` David Hildenbrand
2019-03-28 20:10 ` David Hildenbrand
2019-03-28 20:43 ` Dan Williams
2019-03-28 21:17 ` David Hildenbrand
2019-03-28 21:32 ` Dan Williams
2019-03-28 21:54 ` David Hildenbrand
2019-04-10 9:51 ` David Hildenbrand
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=x494l7rdo5r.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=logang@deltatee.com \
--cc=mhocko@kernel.org \
--cc=stable@vger.kernel.org \
--cc=toshi.kani@hpe.com \
--cc=vbabka@suse.cz \
/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).