All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: hch@lst.de, sfr@canb.auug.org.au, mpe@ellerman.id.au,
	benh@kernel.crashing.org, paulus@samba.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	rth@twiddle.net, ink@jurassic.park.msu.ru, mattst88@gmail.com,
	linux-alpha@vger.kernel.org, tony.luck@intel.com,
	fenghua.yu@intel.com, linux-ia64@vger.kernel.org,
	gerald.schaefer@linux.ibm.com, hca@linux.ibm.com,
	gor@linux.ibm.com, borntraeger@de.ibm.com,
	linux-s390@vger.kernel.org, davem@davemloft.net,
	sparclinux@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de, x86@kernel.org, hpa@zytor.com,
	James.Bottomley@HansenPartnership.com, deller@gmx.de,
	linux-parisc@vger.kernel.org
Subject: Re: [PATCH 0/2] dma-mapping: update default segment_boundary_mask
Date: Wed, 2 Sep 2020 20:26:00 -0700	[thread overview]
Message-ID: <20200903032559.GA4517@Asurada-Nvidia> (raw)
In-Reply-To: <2c8db0aa-e8b5-e577-b971-1de10ecc6747@linux.ibm.com>

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@linux.ibm.com>
 
Thanks for testing and the ack! 

WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: hch@lst.de, sfr@canb.auug.org.au, mpe@ellerman.id.au,
	benh@kernel.crashing.org, paulus@samba.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	rth@twiddle.net, ink@jurassic.park.msu.ru, mattst88@gmail.com,
	linux-alpha@vger.kernel.org, tony.luck@intel.com,
	fenghua.yu@intel.com, linux-ia64@vger.kernel.org,
	gerald.schaefer@linux.ibm.com, hca@linux.ibm.com,
	gor@linux.ibm.com, borntraeger@de.ibm.com,
	linux-s390@vger.kernel.org, davem@davemloft.net,
	sparclinux@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de, x86@kernel.org, hpa@zytor.com,
	James.Bottomley@HansenPartnership.com, deller@gmx.de,
	linux-parisc@vger.kernel.org
Subject: Re: [PATCH 0/2] dma-mapping: update default segment_boundary_mask
Date: Thu, 03 Sep 2020 03:26:00 +0000	[thread overview]
Message-ID: <20200903032559.GA4517@Asurada-Nvidia> (raw)
In-Reply-To: <2c8db0aa-e8b5-e577-b971-1de10ecc6747@linux.ibm.com>

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@linux.ibm.com>
 
Thanks for testing and the ack! 

WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: linux-ia64@vger.kernel.org,
	James.Bottomley@HansenPartnership.com, paulus@samba.org,
	hpa@zytor.com, sparclinux@vger.kernel.org, hch@lst.de,
	sfr@canb.auug.org.au, deller@gmx.de, x86@kernel.org,
	borntraeger@de.ibm.com, mingo@redhat.com, mattst88@gmail.com,
	fenghua.yu@intel.com, gor@linux.ibm.com,
	linux-s390@vger.kernel.org, hca@linux.ibm.com,
	ink@jurassic.park.msu.ru, tglx@linutronix.de,
	gerald.schaefer@linux.ibm.com, rth@twiddle.net,
	tony.luck@intel.com, linux-parisc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
	bp@alien8.de, linuxppc-dev@lists.ozlabs.org, davem@davemloft.net
Subject: Re: [PATCH 0/2] dma-mapping: update default segment_boundary_mask
Date: Wed, 2 Sep 2020 20:26:00 -0700	[thread overview]
Message-ID: <20200903032559.GA4517@Asurada-Nvidia> (raw)
In-Reply-To: <2c8db0aa-e8b5-e577-b971-1de10ecc6747@linux.ibm.com>

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@linux.ibm.com>
 
Thanks for testing and the ack! 

  reply	other threads:[~2020-09-03  3:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 22:16 [PATCH 0/2] dma-mapping: update default segment_boundary_mask Nicolin Chen
2020-09-01 22:16 ` Nicolin Chen
2020-09-01 22:16 ` Nicolin Chen
2020-09-01 22:16 ` [PATCH 1/2] dma-mapping: introduce dma_get_seg_boundary_nr_pages() Nicolin Chen
2020-09-01 22:16   ` Nicolin Chen
2020-09-01 22:16   ` Nicolin Chen
2020-09-03  3:47   ` Michael Ellerman
2020-09-03  3:47     ` Michael Ellerman
2020-09-03  3:47     ` Michael Ellerman
2020-09-03 10:57   ` Andy Shevchenko
2020-09-03 10:57     ` Andy Shevchenko
2020-09-03 10:57     ` Andy Shevchenko
2020-09-03 10:57     ` Andy Shevchenko
2020-09-03 16:12     ` Christoph Hellwig
2020-09-03 16:12       ` Christoph Hellwig
2020-09-03 16:12       ` Christoph Hellwig
2020-09-03 16:12       ` Christoph Hellwig
2020-09-03 17:53       ` Christophe Leroy
2020-09-03 17:53         ` Christophe Leroy
2020-09-03 17:53         ` Christophe Leroy
2020-09-03 17:53         ` Christophe Leroy
2020-09-01 22:16 ` [PATCH 2/2] dma-mapping: set default segment_boundary_mask to ULONG_MAX Nicolin Chen
2020-09-01 22:16   ` Nicolin Chen
2020-09-01 22:16   ` Nicolin Chen
2020-09-02  8:13 ` [PATCH 0/2] dma-mapping: update default segment_boundary_mask Niklas Schnelle
2020-09-02  8:13   ` Niklas Schnelle
2020-09-02  8:13   ` Niklas Schnelle
2020-09-03  3:26   ` Nicolin Chen [this message]
2020-09-03  3:26     ` Nicolin Chen
2020-09-03  3:26     ` Nicolin Chen
2020-09-03 16:13   ` Christoph Hellwig
2020-09-03 16:13     ` Christoph Hellwig
2020-09-03 16:13     ` Christoph Hellwig

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=20200903032559.GA4517@Asurada-Nvidia \
    --to=nicoleotsuka@gmail.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=benh@kernel.crashing.org \
    --cc=borntraeger@de.ibm.com \
    --cc=bp@alien8.de \
    --cc=davem@davemloft.net \
    --cc=deller@gmx.de \
    --cc=fenghua.yu@intel.com \
    --cc=gerald.schaefer@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=hpa@zytor.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mattst88@gmail.com \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    --cc=rth@twiddle.net \
    --cc=schnelle@linux.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sparclinux@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.