Groups > linux.kernel > #1198839

Re: [FYI] tux3: Core changes

From	Jan Kara <jack@suse.cz>
Newsgroups	linux.kernel
Subject	Re: [FYI] tux3: Core changes
Date	2015-08-03 15:10 +0200
Message-ID	<pTnF8-3WH-17@gated-at.bofh.it> (permalink)
References	(5 earlier) <pSnnP-5Ay-11@gated-at.bofh.it> <pSqOK-2jd-11@gated-at.bofh.it> <pSqYq-2uK-13@gated-at.bofh.it> <pSsxc-4OR-19@gated-at.bofh.it> <pSsGS-50d-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Fri 31-07-15 17:16:45, Daniel Phillips wrote:
> On Friday, July 31, 2015 5:00:43 PM PDT, Daniel Phillips wrote:
> >Note: Hirofumi's email is clear, logical and speaks to the
> >question. This branch of the thread is largely pointless, though
> >it essentially says the same thing in non-technical terms. Perhaps
> >your next response should be to Hirofumi, and perhaps it should be
> >technical.
> 
> Now, let me try to lead the way, but being specific. RDMA was raised
> as a potential failure case for Tux3 page forking. But the RDMA api
> does not let you use memory mmaped by Tux3 as a source or destination
> of IO. Instead, it sets up its own pages and hands them out to the
> RDMA app from a pool. So no issue. One down, right?

Can you please tell me how you arrived to that conclusion? As far as I'm
looking at the code in drivers/infiniband/ I don't see anything there
preventing userspace from passing in mmapped memory...

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Thread

Re: [FYI] tux3: Core changes OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> - 2015-07-31 06:50 +0200
  Re: [FYI] tux3: Core changes Jan Kara <jack@suse.cz> - 2015-08-03 15:10 +0200
  Re: [FYI] tux3: Core changes Jan Kara <jack@suse.cz> - 2015-08-03 15:50 +0200

csiph-web