From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Roland Dreier <roland@kernel.org>,
linux-rdma@vger.kernel.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Infiniband use of get_user_pages()
Date: Fri, 26 Apr 2013 13:19:04 -0400 [thread overview]
Message-ID: <CAHGf_=rRomz4r8c5nJ8edX29bpwxA4T4bFOq3rW2FgOuVSkLFw@mail.gmail.com> (raw)
In-Reply-To: <20130424153810.GA25958@quack.suse.cz>
> when checking users of get_user_pages() (I'm doing some cleanups in that
> area to fix filesystem's issues with mmap_sem locking) I've noticed that
> infiniband drivers add number of pages obtained from get_user_pages() to
> mm->pinned_vm counter. Although this makes some sence, it doesn't match
> with any other user of get_user_pages() (e.g. direct IO) so has infiniband
> some special reason why it does so?
I'm also puzzled because mm->pinned_vm_counter is only used from /proc. Who
and how to use this accounting?
> Also that seems to be the only real reason why mmap_sem has to be grabbed
> in exclusive mode, am I right?
I think so. get_user_pages() doesn't need write lock.
> Another suspicious thing (at least in drivers/infiniband/core/umem.c:
> ib_umem_get()) is that arguments of get_user_pages() are like:
> ret = get_user_pages(current, current->mm, cur_base,
> min_t(unsigned long, npages,
> PAGE_SIZE / sizeof (struct page *)),
> 1, !umem->writable, page_list, vma_list);
> So we always have write argument set to 1 and force argument is set to
> !umem->writable. Is that really intentional? My naive guess would be that
> arguments should be switched... Although even in that case I fail to see
> why 'force' argument should be set. Can someone please explain?
If I understand correctly, IB and DirectIO have different set sequence.
DirectIO
1. write to buf
2. write(buf). i.e. get_user_pages_fast(write=0)
Infiniband
1. reg_mr. i.e. get_user_pages(write=1)
2. write to buf
I mean, if direct-io is passed zero page, it is user mistake. but user
process which uses infiniband set up mr before writing IO buffer,
IIUC.
In this case, I think user process which uses infiniband need to dereg
mr before fork(). but it is another story.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2013-04-26 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 15:38 Jan Kara
2013-04-24 15:43 ` Christoph Lameter
2013-04-24 22:25 ` Roland Dreier
2013-04-25 13:21 ` Jan Kara
2013-04-29 18:44 ` Roland Dreier
2013-04-26 17:19 ` KOSAKI Motohiro [this message]
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='CAHGf_=rRomz4r8c5nJ8edX29bpwxA4T4bFOq3rW2FgOuVSkLFw@mail.gmail.com' \
--to=kosaki.motohiro@gmail.com \
--cc=jack@suse.cz \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=roland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox