From: Ira Weiny <ira.weiny@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fbdev@vger.kernel.org, Michal Hocko <mhocko@suse.com>,
kvm@vger.kernel.org, linux-sh@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
James Hogan <jhogan@kernel.org>,
linux-fpga@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>,
dri-devel@lists.freedesktop.org, linux-mips@vger.kernel.org,
linux-mm@kvack.org, Rich Felker <dalias@libc.org>,
Paul Mackerras <paulus@samba.org>,
sparclinux@vger.kernel.org, ceph-devel@vger.kernel.org,
devel@driverdev.osuosl.org, linux-s390@vger.kernel.org,
rds-devel@oss.oracle.com,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-rdma@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>,
Ingo Molnar <mingo@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
xen-devel@lists.xenproject.org, devel@lists.orangefs.org,
linux-media@vger.kernel.org, John Hubbard <jhubbard@nvidia.com>,
kvm-ppc@vger.kernel.org, Borislav
Subject: Re: [RESEND PATCH 0/7] Add FOLL_LONGTERM to GUP fast and use it
Date: Wed, 20 Feb 2019 18:02:56 +0000 [thread overview]
Message-ID: <20190220180255.GA12020@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <20190220151930.GB11695@infradead.org>
On Wed, Feb 20, 2019 at 07:19:30AM -0800, Christoph Hellwig wrote:
> On Tue, Feb 19, 2019 at 09:30:33PM -0800, ira.weiny@intel.com wrote:
> > From: Ira Weiny <ira.weiny@intel.com>
> >
> > Resending these as I had only 1 minor comment which I believe we have covered
> > in this series. I was anticipating these going through the mm tree as they
> > depend on a cleanup patch there and the IB changes are very minor. But they
> > could just as well go through the IB tree.
> >
> > NOTE: This series depends on my clean up patch to remove the write parameter
> > from gup_fast_permitted()[1]
> >
> > HFI1, qib, and mthca, use get_user_pages_fast() due to it performance
> > advantages. These pages can be held for a significant time. But
> > get_user_pages_fast() does not protect against mapping of FS DAX pages.
>
> This I don't get - if you do lock down long term mappings performance
> of the actual get_user_pages call shouldn't matter to start with.
>
> What do I miss?
A couple of points.
First "longterm" is a relative thing and at this point is probably a misnomer.
This is really flagging a pin which is going to be given to hardware and can't
move. I've thought of a couple of alternative names but I think we have to
settle on if we are going to use FL_LAYOUT or something else to solve the
"longterm" problem. Then I think we can change the flag to a better name.
Second, It depends on how often you are registering memory. I have spoken with
some RDMA users who consider MR in the performance path... For the overall
application performance. I don't have the numbers as the tests for HFI1 were
done a long time ago. But there was a significant advantage. Some of which is
probably due to the fact that you don't have to hold mmap_sem.
Finally, architecturally I think it would be good for everyone to use *_fast.
There are patches submitted to the RDMA list which would allow the use of
*_fast (they reworking the use of mmap_sem) and as soon as they are accepted
I'll submit a patch to convert the RDMA core as well. Also to this point
others are looking to use *_fast.[2]
As an asside, Jasons pointed out in my previous submission that *_fast and
*_unlocked look very much the same. I agree and I think further cleanup will
be coming. But I'm focused on getting the final solution for DAX at the
moment.
Ira
WARNING: multiple messages have this Message-ID (diff)
From: Ira Weiny <ira.weiny@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fbdev@vger.kernel.org, Michal Hocko <mhocko@suse.com>,
kvm@vger.kernel.org, linux-sh@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
James Hogan <jhogan@kernel.org>,
linux-fpga@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>,
dri-devel@lists.freedesktop.org, linux-mips@vger.kernel.org,
linux-mm@kvack.org, Rich Felker <dalias@libc.org>,
Paul Mackerras <paulus@samba.org>,
sparclinux@vger.kernel.org, ceph-devel@vger.kernel.org,
devel@driverdev.osuosl.org, linux-s390@vger.kernel.org,
rds-devel@oss.oracle.com,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-rdma@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>,
Ingo Molnar <mingo@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
xen-devel@lists.xenproject.org, devel@lists.orangefs.org,
linux-media@vger.kernel.org, John Hubbard <jhubbard@nvidia.com>,
kvm-ppc@vger.kernel.org, Borislav
Subject: Re: [RESEND PATCH 0/7] Add FOLL_LONGTERM to GUP fast and use it
Date: Wed, 20 Feb 2019 10:02:56 -0800 [thread overview]
Message-ID: <20190220180255.GA12020@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <20190220151930.GB11695@infradead.org>
On Wed, Feb 20, 2019 at 07:19:30AM -0800, Christoph Hellwig wrote:
> On Tue, Feb 19, 2019 at 09:30:33PM -0800, ira.weiny@intel.com wrote:
> > From: Ira Weiny <ira.weiny@intel.com>
> >
> > Resending these as I had only 1 minor comment which I believe we have covered
> > in this series. I was anticipating these going through the mm tree as they
> > depend on a cleanup patch there and the IB changes are very minor. But they
> > could just as well go through the IB tree.
> >
> > NOTE: This series depends on my clean up patch to remove the write parameter
> > from gup_fast_permitted()[1]
> >
> > HFI1, qib, and mthca, use get_user_pages_fast() due to it performance
> > advantages. These pages can be held for a significant time. But
> > get_user_pages_fast() does not protect against mapping of FS DAX pages.
>
> This I don't get - if you do lock down long term mappings performance
> of the actual get_user_pages call shouldn't matter to start with.
>
> What do I miss?
A couple of points.
First "longterm" is a relative thing and at this point is probably a misnomer.
This is really flagging a pin which is going to be given to hardware and can't
move. I've thought of a couple of alternative names but I think we have to
settle on if we are going to use FL_LAYOUT or something else to solve the
"longterm" problem. Then I think we can change the flag to a better name.
Second, It depends on how often you are registering memory. I have spoken with
some RDMA users who consider MR in the performance path... For the overall
application performance. I don't have the numbers as the tests for HFI1 were
done a long time ago. But there was a significant advantage. Some of which is
probably due to the fact that you don't have to hold mmap_sem.
Finally, architecturally I think it would be good for everyone to use *_fast.
There are patches submitted to the RDMA list which would allow the use of
*_fast (they reworking the use of mmap_sem) and as soon as they are accepted
I'll submit a patch to convert the RDMA core as well. Also to this point
others are looking to use *_fast.[2]
As an asside, Jasons pointed out in my previous submission that *_fast and
*_unlocked look very much the same. I agree and I think further cleanup will
be coming. But I'm focused on getting the final solution for DAX at the
moment.
Ira
WARNING: multiple messages have this Message-ID (diff)
From: Ira Weiny <ira.weiny@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: John Hubbard <jhubbard@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
"David S. Miller" <davem@davemloft.net>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Rich Felker <dalias@libc.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
James Hogan <jhogan@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
sparclinux@vger.kernel.org, kvm-ppc@vger.kernel.org,
kvm@vger.kernel.org, linux-fpga@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-rdma@vger.kernel.org,
linux-media@vger.kernel.org, linux-scsi@vger.kernel.org,
devel@driverdev.osuosl.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-fbdev@vger.kernel.org,
xen-devel@lists.xenproject.org, devel@lists.orangefs.org,
ceph-devel@vger.kernel.org, rds-devel@oss.oracle.com
Subject: Re: [RESEND PATCH 0/7] Add FOLL_LONGTERM to GUP fast and use it
Date: Wed, 20 Feb 2019 10:02:56 -0800 [thread overview]
Message-ID: <20190220180255.GA12020@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <20190220151930.GB11695@infradead.org>
On Wed, Feb 20, 2019 at 07:19:30AM -0800, Christoph Hellwig wrote:
> On Tue, Feb 19, 2019 at 09:30:33PM -0800, ira.weiny@intel.com wrote:
> > From: Ira Weiny <ira.weiny@intel.com>
> >
> > Resending these as I had only 1 minor comment which I believe we have covered
> > in this series. I was anticipating these going through the mm tree as they
> > depend on a cleanup patch there and the IB changes are very minor. But they
> > could just as well go through the IB tree.
> >
> > NOTE: This series depends on my clean up patch to remove the write parameter
> > from gup_fast_permitted()[1]
> >
> > HFI1, qib, and mthca, use get_user_pages_fast() due to it performance
> > advantages. These pages can be held for a significant time. But
> > get_user_pages_fast() does not protect against mapping of FS DAX pages.
>
> This I don't get - if you do lock down long term mappings performance
> of the actual get_user_pages call shouldn't matter to start with.
>
> What do I miss?
A couple of points.
First "longterm" is a relative thing and at this point is probably a misnomer.
This is really flagging a pin which is going to be given to hardware and can't
move. I've thought of a couple of alternative names but I think we have to
settle on if we are going to use FL_LAYOUT or something else to solve the
"longterm" problem. Then I think we can change the flag to a better name.
Second, It depends on how often you are registering memory. I have spoken with
some RDMA users who consider MR in the performance path... For the overall
application performance. I don't have the numbers as the tests for HFI1 were
done a long time ago. But there was a significant advantage. Some of which is
probably due to the fact that you don't have to hold mmap_sem.
Finally, architecturally I think it would be good for everyone to use *_fast.
There are patches submitted to the RDMA list which would allow the use of
*_fast (they reworking the use of mmap_sem) and as soon as they are accepted
I'll submit a patch to convert the RDMA core as well. Also to this point
others are looking to use *_fast.[2]
As an asside, Jasons pointed out in my previous submission that *_fast and
*_unlocked look very much the same. I agree and I think further cleanup will
be coming. But I'm focused on getting the final solution for DAX at the
moment.
Ira
WARNING: multiple messages have this Message-ID (diff)
From: Ira Weiny <ira.weiny@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fbdev@vger.kernel.org, Michal Hocko <mhocko@suse.com>,
kvm@vger.kernel.org, linux-sh@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
James Hogan <jhogan@kernel.org>,
linux-fpga@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>,
dri-devel@lists.freedesktop.org, linux-mips@vger.kernel.org,
linux-mm@kvack.org, Rich Felker <dalias@libc.org>,
Paul Mackerras <paulus@samba.org>,
sparclinux@vger.kernel.org, ceph-devel@vger.kernel.org,
devel@driverdev.osuosl.org, linux-s390@vger.kernel.org,
rds-devel@oss.oracle.com,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-rdma@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>,
Ingo Molnar <mingo@redhat.com>,
xen-devel@lists.xenproject.org, devel@lists.orangefs.org,
linux-media@vger.kernel.org, John Hubbard <jhubbard@nvidia.com>,
kvm-ppc@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
virtualization@lists.linux-foundation.org,
linux-scsi@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [RESEND PATCH 0/7] Add FOLL_LONGTERM to GUP fast and use it
Date: Wed, 20 Feb 2019 10:02:56 -0800 [thread overview]
Message-ID: <20190220180255.GA12020@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <20190220151930.GB11695@infradead.org>
On Wed, Feb 20, 2019 at 07:19:30AM -0800, Christoph Hellwig wrote:
> On Tue, Feb 19, 2019 at 09:30:33PM -0800, ira.weiny@intel.com wrote:
> > From: Ira Weiny <ira.weiny@intel.com>
> >
> > Resending these as I had only 1 minor comment which I believe we have covered
> > in this series. I was anticipating these going through the mm tree as they
> > depend on a cleanup patch there and the IB changes are very minor. But they
> > could just as well go through the IB tree.
> >
> > NOTE: This series depends on my clean up patch to remove the write parameter
> > from gup_fast_permitted()[1]
> >
> > HFI1, qib, and mthca, use get_user_pages_fast() due to it performance
> > advantages. These pages can be held for a significant time. But
> > get_user_pages_fast() does not protect against mapping of FS DAX pages.
>
> This I don't get - if you do lock down long term mappings performance
> of the actual get_user_pages call shouldn't matter to start with.
>
> What do I miss?
A couple of points.
First "longterm" is a relative thing and at this point is probably a misnomer.
This is really flagging a pin which is going to be given to hardware and can't
move. I've thought of a couple of alternative names but I think we have to
settle on if we are going to use FL_LAYOUT or something else to solve the
"longterm" problem. Then I think we can change the flag to a better name.
Second, It depends on how often you are registering memory. I have spoken with
some RDMA users who consider MR in the performance path... For the overall
application performance. I don't have the numbers as the tests for HFI1 were
done a long time ago. But there was a significant advantage. Some of which is
probably due to the fact that you don't have to hold mmap_sem.
Finally, architecturally I think it would be good for everyone to use *_fast.
There are patches submitted to the RDMA list which would allow the use of
*_fast (they reworking the use of mmap_sem) and as soon as they are accepted
I'll submit a patch to convert the RDMA core as well. Also to this point
others are looking to use *_fast.[2]
As an asside, Jasons pointed out in my previous submission that *_fast and
*_unlocked look very much the same. I agree and I think further cleanup will
be coming. But I'm focused on getting the final solution for DAX at the
moment.
Ira
next prev parent reply other threads:[~2019-02-20 18:02 UTC|newest]
Thread overview: 188+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 5:30 [RESEND PATCH 0/7] Add FOLL_LONGTERM to GUP fast and use it ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` [RESEND PATCH 1/7] mm/gup: Replace get_user_pages_longterm() with FOLL_LONGTERM ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` [RESEND PATCH 2/7] mm/gup: Change write parameter to flags in fast walk ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` [RESEND PATCH 3/7] mm/gup: Change GUP fast to use flags rather than a write 'bool' ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 19:29 ` Mike Marshall
2019-02-20 19:29 ` Mike Marshall
2019-02-20 19:29 ` Mike Marshall
2019-02-20 19:29 ` Mike Marshall
2019-02-20 19:29 ` Mike Marshall
2019-02-20 19:29 ` Mike Marshall
2019-02-21 3:18 ` Souptick Joarder
2019-02-21 3:18 ` Souptick Joarder
2019-02-21 3:30 ` Souptick Joarder
2019-02-21 3:18 ` Souptick Joarder
2019-02-21 3:18 ` Souptick Joarder
2019-02-21 3:18 ` Souptick Joarder
2019-02-21 22:24 ` Ira Weiny
2019-02-21 22:24 ` Ira Weiny
2019-02-21 22:24 ` Ira Weiny
2019-02-21 22:24 ` Ira Weiny
2019-02-21 22:24 ` Ira Weiny
2019-02-20 5:30 ` [RESEND PATCH 4/7] mm/gup: Add FOLL_LONGTERM capability to GUP fast ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` [RESEND PATCH 5/7] IB/hfi1: Use the new FOLL_LONGTERM flag to get_user_pages_fast() ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` [RESEND PATCH 6/7] IB/qib: " ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` [RESEND PATCH 7/7] IB/mthca: " ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 5:30 ` ira.weiny
2019-02-20 15:19 ` [RESEND PATCH 0/7] Add FOLL_LONGTERM to GUP fast and use it Christoph Hellwig
2019-02-20 15:19 ` Christoph Hellwig
2019-02-20 15:19 ` Christoph Hellwig
2019-02-20 15:19 ` Christoph Hellwig
2019-02-20 18:02 ` Ira Weiny [this message]
2019-02-20 18:02 ` Ira Weiny
2019-02-20 18:02 ` Ira Weiny
2019-02-20 18:02 ` Ira Weiny
2019-02-20 18:02 ` Ira Weiny
2019-02-20 15:19 ` Christoph Hellwig
2019-02-20 15:19 ` Christoph Hellwig
2019-02-27 19:14 ` Ira Weiny
2019-02-27 19:14 ` Ira Weiny
2019-02-27 19:14 ` Ira Weiny
2019-02-27 19:14 ` Ira Weiny
2019-02-27 19:14 ` Ira Weiny
2019-03-17 18:34 ` ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-17 18:34 ` [RESEND 1/7] mm/gup: Replace get_user_pages_longterm() with FOLL_LONGTERM ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-22 21:24 ` Dan Williams
2019-03-22 21:24 ` Dan Williams
2019-03-22 21:24 ` Dan Williams
2019-03-22 21:24 ` Dan Williams
2019-03-22 21:24 ` Dan Williams
2019-03-25 6:19 ` Ira Weiny
2019-03-25 6:19 ` Ira Weiny
2019-03-25 6:19 ` Ira Weiny
2019-03-25 6:19 ` Ira Weiny
2019-03-25 16:45 ` Dan Williams
2019-03-25 16:45 ` Dan Williams
2019-03-25 16:45 ` Dan Williams
2019-03-25 16:45 ` Dan Williams
2019-03-25 16:45 ` Dan Williams
2019-03-25 8:46 ` Ira Weiny
2019-03-25 8:46 ` Ira Weiny
2019-03-25 8:46 ` Ira Weiny
2019-03-25 8:46 ` Ira Weiny
2019-03-25 10:27 ` Ira Weiny
2019-03-25 10:27 ` Ira Weiny
2019-03-25 10:27 ` Ira Weiny
2019-03-25 10:27 ` Ira Weiny
2019-03-17 18:34 ` [RESEND 2/7] mm/gup: Change write parameter to flags in fast walk ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-22 21:30 ` Dan Williams
2019-03-22 21:30 ` Dan Williams
2019-03-22 21:30 ` Dan Williams
2019-03-22 21:30 ` Dan Williams
2019-03-22 21:30 ` Dan Williams
2019-03-17 18:34 ` [RESEND 3/7] mm/gup: Change GUP fast to use flags rather than a write 'bool' ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-22 22:05 ` Dan Williams
2019-03-22 22:05 ` Dan Williams
2019-03-22 22:05 ` Dan Williams
2019-03-22 22:05 ` Dan Williams
2019-03-22 22:05 ` Dan Williams
2019-03-25 8:26 ` Ira Weiny
2019-03-25 8:26 ` Ira Weiny
2019-03-25 8:26 ` Ira Weiny
2019-03-25 8:26 ` Ira Weiny
2019-03-17 18:34 ` [RESEND 4/7] mm/gup: Add FOLL_LONGTERM capability to GUP fast ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-22 22:12 ` Dan Williams
2019-03-22 22:12 ` Dan Williams
2019-03-22 22:12 ` Dan Williams
2019-03-22 22:12 ` Dan Williams
2019-03-22 22:12 ` Dan Williams
2019-03-25 8:42 ` Ira Weiny
2019-03-25 8:42 ` Ira Weiny
2019-03-25 8:42 ` Ira Weiny
2019-03-25 8:42 ` Ira Weiny
2019-03-25 16:47 ` Jason Gunthorpe
2019-03-25 16:47 ` Jason Gunthorpe
2019-03-25 16:47 ` Jason Gunthorpe
2019-03-25 16:47 ` Jason Gunthorpe
2019-03-25 9:23 ` Ira Weiny
2019-03-25 9:23 ` Ira Weiny
2019-03-25 9:23 ` Ira Weiny
2019-03-25 9:23 ` Ira Weiny
2019-03-25 17:51 ` Jason Gunthorpe
2019-03-25 17:51 ` Jason Gunthorpe
2019-03-25 17:51 ` Jason Gunthorpe
2019-03-25 17:51 ` Jason Gunthorpe
2019-03-25 14:21 ` Ira Weiny
2019-03-25 14:21 ` Ira Weiny
2019-03-25 14:21 ` Ira Weiny
2019-03-25 14:21 ` Ira Weiny
2019-03-25 22:36 ` Dan Williams
2019-03-25 22:36 ` Dan Williams
2019-03-25 22:36 ` Dan Williams
2019-03-25 22:36 ` Dan Williams
2019-03-25 22:36 ` Dan Williams
2019-03-25 14:54 ` Ira Weiny
2019-03-25 14:54 ` Ira Weiny
2019-03-25 14:54 ` Ira Weiny
2019-03-25 14:54 ` Ira Weiny
2019-03-17 18:34 ` [RESEND 5/7] IB/hfi1: Use the new FOLL_LONGTERM flag to get_user_pages_fast() ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-22 22:14 ` Dan Williams
2019-03-22 22:14 ` Dan Williams
2019-03-22 22:14 ` Dan Williams
2019-03-22 22:14 ` Dan Williams
2019-03-22 22:14 ` Dan Williams
2019-03-25 8:43 ` Ira Weiny
2019-03-25 8:43 ` Ira Weiny
2019-03-25 8:43 ` Ira Weiny
2019-03-25 8:43 ` Ira Weiny
2019-03-17 18:34 ` [RESEND 6/7] IB/qib: " ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-22 22:15 ` Dan Williams
2019-03-22 22:15 ` Dan Williams
2019-03-22 22:15 ` Dan Williams
2019-03-22 22:15 ` Dan Williams
2019-03-22 22:15 ` Dan Williams
2019-03-17 18:34 ` [RESEND 7/7] IB/mthca: " ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-17 18:34 ` ira.weiny
2019-03-19 22:19 ` [RESEND PATCH 0/7] Add FOLL_LONGTERM to GUP fast and use it Andrew Morton
2019-03-19 22:19 ` Andrew Morton
2019-03-19 22:19 ` Andrew Morton
2019-03-19 22:19 ` Andrew Morton
2019-03-21 8:40 ` Ira Weiny
2019-03-21 8:40 ` Ira Weiny
2019-03-21 8:40 ` Ira Weiny
2019-03-21 8:40 ` Ira Weiny
2019-02-20 5:30 ira.weiny
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=20190220180255.GA12020@iweiny-DESK2.sc.intel.com \
--to=ira.weiny@intel.com \
--cc=benh@kernel.crashing.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dalias@libc.org \
--cc=devel@driverdev.osuosl.org \
--cc=devel@lists.orangefs.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@infradead.org \
--cc=heiko.carstens@de.ibm.com \
--cc=jgg@ziepe.ca \
--cc=jhogan@kernel.org \
--cc=jhubbard@nvidia.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rds-devel@oss.oracle.com \
--cc=sparclinux@vger.kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=ysato@users.sourceforge.jp \
/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.