The original message was received at Sun, 5 May 2019 11:30:54 +0800
from lists.01.org [111.40.227.101]
- The following addresses had permanent fatal errors -
- Transcript of session follows -
while talking to lists.01.org.:
>>> MAIL From:"Post Office"
<<< 501 "Post Office"
On Fri, Mar 15, 2019 at 01:26:04PM +1100, Dave Chinner wrote:
> On Thu, Mar 14, 2019 at 12:34:51AM -0700, Dan Williams wrote:
> > On Mon, Mar 11, 2019 at 9:38 PM Dave Chinner wrote:
> > >
> > > On Mon, Mar 11, 2019 at 08:35:05PM -0700, Dan Williams wrote:
> > > > On Mon, Mar 11, 2019 at 8:10 AM
On Sat, May 4, 2019, 3:26 PM Dan Williams wrote:
> On Thu, May 2, 2019 at 9:12 AM Pavel Tatashin
> wrote:
> >
> > On Wed, Apr 17, 2019 at 2:53 PM Dan Williams
> wrote:
> > >
> > > Prepare for hot{plug,remove} of sub-ranges of a section by tracking a
> > > section active bitmask, each bit
On Thu, May 2, 2019 at 9:12 AM Pavel Tatashin wrote:
>
> On Wed, Apr 17, 2019 at 2:53 PM Dan Williams wrote:
> >
> > Prepare for hot{plug,remove} of sub-ranges of a section by tracking a
> > section active bitmask, each bit representing 2MB (SECTION_SIZE (128M) /
> > map_active bitmask length
> > I'm ok with it being 16M for now unless it causes a problem in
> > practice, i.e. something like the minimum hardware mapping alignment
> > for physical memory being less than 16M.
>
> On second thought, arbitrary differences across architectures is a bit
> sad. The most common nvdimm
On Fri, May 03, 2019 at 04:14:49PM -0700, Brendan Higgins wrote:
> In any case, it sounds like you and Greg are in agreement on the core
> libraries generating the output in TAP13, so I won't argue that point
> further.
Great!
> ## Analysis of using TAP13
>
> One of my earlier concerns was that
On Fri, May 03, 2019 at 04:41:10PM -0700, Brendan Higgins wrote:
> > On Thu, May 02, 2019 at 11:45:43AM -0700, Brendan Higgins wrote:
> > > On Thu, May 2, 2019 at 11:15 AM wrote:
> > > >
> > > >
> > > >
> > > > > -Original Message-
> > > > > From: Greg KH
> > > > >
> > > > > On Wed, May
