[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200903032559.GA4517@Asurada-Nvidia>
Date: Wed, 2 Sep 2020 20:26:00 -0700
From: Nicolin Chen <nicoleotsuka@...il.com>
To: Niklas Schnelle <schnelle@...ux.ibm.com>
Cc: hch@....de, sfr@...b.auug.org.au, mpe@...erman.id.au,
benh@...nel.crashing.org, paulus@...ba.org,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
rth@...ddle.net, ink@...assic.park.msu.ru, mattst88@...il.com,
linux-alpha@...r.kernel.org, tony.luck@...el.com,
fenghua.yu@...el.com, linux-ia64@...r.kernel.org,
gerald.schaefer@...ux.ibm.com, hca@...ux.ibm.com,
gor@...ux.ibm.com, borntraeger@...ibm.com,
linux-s390@...r.kernel.org, davem@...emloft.net,
sparclinux@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
bp@...en8.de, x86@...nel.org, hpa@...or.com,
James.Bottomley@...senPartnership.com, deller@....de,
linux-parisc@...r.kernel.org
Subject: Re: [PATCH 0/2] dma-mapping: update default segment_boundary_mask
On Wed, Sep 02, 2020 at 10:13:12AM +0200, Niklas Schnelle wrote:
> On 9/2/20 12:16 AM, Nicolin Chen wrote:
> > These two patches are to update default segment_boundary_mask.
> >
> > PATCH-1 fixes overflow issues in callers of dma_get_seg_boundary.
> > Previous version was a series: https://lkml.org/lkml/2020/8/31/1026
> >
> > Then PATCH-2 sets default segment_boundary_mask to ULONG_MAX.
> >
> > Nicolin Chen (2):
> > dma-mapping: introduce dma_get_seg_boundary_nr_pages()
> > dma-mapping: set default segment_boundary_mask to ULONG_MAX
>
> I gave both of your patches a quick test ride on a couple of dev mainframes,
> both NVMe, ConnectX and virtio-pci devices all seems to work fine.
> I already commented on Christoph's mail that I like the helper approach,
> so as for s390 you can add my
>
> Acked-by: Niklas Schnelle <schnelle@...ux.ibm.com>
Thanks for testing and the ack!
Powered by blists - more mailing lists