On 21.05.2019 19:43, Andy Lutomirski wrote:
> On Tue, May 21, 2019 at 8:52 AM Kirill Tkhai <ktkhai@xxxxxxxxxxxxx> wrote:
>>
>> On 21.05.2019 17:43, Andy Lutomirski wrote:
>>> On Mon, May 20, 2019 at 7:01 AM Kirill Tkhai <ktkhai@xxxxxxxxxxxxx> wrote:
>>>>
>>>
>>>> [Summary]
>>>>
>>>> New syscall, which allows to clone a remote process VMA
>>>> into local process VM. The remote process's page table
>>>> entries related to the VMA are cloned into local process's
>>>> page table (in any desired address, which makes this different
>>>> from that happens during fork()). Huge pages are handled
>>>> appropriately.
>>>>
>>>> This allows to improve performance in significant way like
>>>> it's shows in the example below.
>>>>
>>>> [Description]
>>>>
>>>> This patchset adds a new syscall, which makes possible
>>>> to clone a VMA from a process to current process.
>>>> The syscall supplements the functionality provided
>>>> by process_vm_writev() and process_vm_readv() syscalls,
>>>> and it may be useful in many situation.
>>>>
>>>> For example, it allows to make a zero copy of data,
>>>> when process_vm_writev() was previously used:
>>>>
>>>> struct iovec local_iov, remote_iov;
>>>> void *buf;
>>>>
>>>> buf = mmap(NULL, n * PAGE_SIZE, PROT_READ|PROT_WRITE,
>>>> MAP_PRIVATE|MAP_ANONYMOUS, ...);
>>>> recv(sock, buf, n * PAGE_SIZE, 0);
>>>>
>>>> local_iov->iov_base = buf;
>>>> local_iov->iov_len = n * PAGE_SIZE;
>>>> remove_iov = ...;
>>>>
>>>> process_vm_writev(pid, &local_iov, 1, &remote_iov, 1 0);
>>>> munmap(buf, n * PAGE_SIZE);
>>>>
>>>> (Note, that above completely ignores error handling)
>>>>
>>>> There are several problems with process_vm_writev() in this example:
>>>>
>>>> 1)it causes pagefault on remote process memory, and it forces
>>>> allocation of a new page (if was not preallocated);
>>>
>>> I don't see how your new syscall helps. You're writing to remote
>>> memory. If that memory wasn't allocated, it's going to get allocated
>>> regardless of whether you use a write-like interface or an mmap-like
>>> interface.
>>
>> No, the talk is not about just another interface for copying memory.
>> The talk is about borrowing of remote task's VMA and corresponding
>> page table's content. Syscall allows to copy part of page table
>> with preallocated pages from remote to local process. See here:
>>
>> [task1] [task2]
>>
>> buf = mmap(NULL, n * PAGE_SIZE, PROT_READ|PROT_WRITE,
>> MAP_PRIVATE|MAP_ANONYMOUS, ...);
>>
>> <task1 populates buf>
>>
>> buf = process_vm_mmap(pid_of_task1, addr, n * PAGE_SIZE, ...);
>> munmap(buf);
>>
>>
>> process_vm_mmap() copies PTEs related to memory of buf in task1 to task2
>> just like in the way we do during fork syscall.
>
> If I understand this correctly, your intended use is to have one task
> allocate memory and fill it, have the other task clone the VMA, and
> have the first task free the VMA? If so, that wasn't at all obvious
> from your original email.
Yes, exactly this. Sorry for confusing in initial description, it's not intentionally.
> Why don't you use splice() instead?
I just don't see a possibility of anonymous memory may be moved from
one process to another via splice(). Maybe you may explain your idea
more detailed?
> splice() the data to the remote
> task and have the remove task read() it? All these VMA games will
> result in a lot of flushes, which is bad for performance. Or,
> depending on your exact constraints, you could map a memfd in both
> tasks instead, which has the same flushing issues but at least has a
> sensible API.
memfd() is file-backed mapping, and it is not suitable for that.
In case of a process had anonymous mapping before the migration,
it wants the mapping remains the same after the migration. So,
if we use memfd(), we have to copy the memory from memfd mapping
to its real anonymous mapping target, which has the same problems
as process_vm_writev().
>>
>> There is no copying of buf memory content, unless COW happens. This is
>> the principal difference to process_vm_writev(), which just allocates
>> pages in remote VM.
>>
>>> Keep in mind that, on x86, just the hardware part of a
>>> page fault is very slow -- populating the memory with a syscall
>>> instead of a fault may well be faster.
>>
>> It is not as slow, as disk IO has. Just compare, what happens in case of anonymous
>> pages related to buf of task1 are swapped:
>>
>> 1)process_vm_writev() reads them back into memory;
>>
>> 2)process_vm_mmap() just copies swap PTEs from task1 page table
>> to task2 page table.
>>
>> Also, for faster page faults one may use huge pages for the mappings.
>> But really, it's funny to think about page faults, when there are
>> disk IO problems I shown.
>
> What are you doing that is causing *disk* IO in any of this? I
> suspect your real problem is that you are using far too large of a
> buffer. See below.
Imagine, we are migrating a container, which consists of 9 GB of pages,
and we have 8GB RAM on destination node. Before the migration, we had
some of pages in RAM and some of pages in swap.
Source node sends pages to destination node. And there are limitations,
which do not allow to start creation of process tree on the destination
node, before all memory is received.
Pages are received by some page server task on destination. After all pages
are received, we create process tree and populate container tasks mappings.
When we're populating tasks mapping, we have to copy memory from page server
to a target task. In case of the pages were swapped from page server's
address space, we have to read synchronously them from swap. This introduces
big latency, and big IO I talked.
>
>>
>>>>
>>>> 2)amount of memory for this example is doubled in a moment --
>>>> n pages in current and n pages in remote tasks are occupied
>>>> at the same time;
>>>
>>> This seems disingenuous. If you're writing p pages total in chunks of
>>> n pages, you will use a total of p pages if you use mmap and p+n if
>>> you use write.
>>
>> I didn't understand this sentence because of many ifs, sorry. Could you
>> please explain your thought once again?
>
> You seem to have a function that tries to populate p pages of memory
> with data received from a socket. It looks like you're doing
> something like this:
>
> void copy_p_pages(size_t p)
> {
> size_t n = some_value(p);
> char *buf = malloc(n * PAGE_SIZE);
> for (int i = 0; i < p; i += n*PAGE_SIZE) {
> read(fd, buf, n*PAGE_SIZE); /* check return value, etc */
> process_vm_writev(write n*PAGE_SIZE bytes to remote process);
> }
> free(buf);
> }
>
> If you have a *constant* n (i.e. some_value(p) is just a number like
> 16)), then you aren't doubling memory usage. If you have
> some_value(p) return p, then you are indeed doubling memory usage. So
> don't do that!
> If buf is getting swapped out, you are very likely doing something
> wrong. If you're using a 100MB buffer or a 10GB, then I'm not
> surprised you have problems. Try something reasonable like 128kB. For
> extra fun, you could mlock() that buf, but if you're thrashing on
> access to a 128kB working set, you will probably also get your *code*
> swapped out, in which case you pretty much lose.
The thing is we can't use small buffer. We have to receive all the restored
tasks pages on the destination node, before we start the process tree
creation like I wrote above. All the anonymous memory is mapped into
page server's MM, so it becomes swapped before container's process
tree starts to create.
>>> For example, if the remote VMA is MAP_ANONYMOUS, do you get
>>> a CoW copy of it? I assume you don't since the whole point is to
>>> write to remote memory
>>
>> But, no, there *is* COW semantic. We do not copy memory. We copy
>> page table content. This is just the same we have on fork(), when
>> children duplicates parent's VMA and related page table subset,
>> and parent's PTEs lose _PAGE_RW flag.
>
> Then you need to document this very carefully, because other people
> will use your syscall in different ways than you use it.
Ok, I'll do.
> And, if you are doing CoW like this, then your syscall is basically
> only useful for your really weird use case in which you're using it to
> import an already-populated VMA. Maybe this is a reasonable feature
> to add to the kernel, but it needs a benchmark against a reasonable
> alternative.
Do you mean comparison with process_vm_writev/readv() or something like
this?
>>
>> There is all copy_page_range() code reused for that. Please, see [3/7]
>> for the details.
>
> You can't as users of a syscall to read the nitty gritty mm code to
> figure out what the syscall does from a user's perspective.
Yeah, sure :)
>>> But there are plenty of other questions.
>>> What happens if the remote VMA is a gate area or other special mapping
>>> (vDSO, vvar area, etc)? What if the remote memory comes from a driver
>>> that wasn't expecting the mapping to get magically copied to a
>>> different process?
>>
>> In case of someone wants to duplicate such the mappings, we may consider
>> that, and extend the interface in the future for VMA types, which are
>> safe for that.
>
> Do you mean that the code you sent rejects this case? If so, please
> document it. In any case, I looked at the code, and it seems to be
> trying to handle MAP_SHARED and MAP_ANONYMOUS. I don't see where it
> would reject copying a vDSO.
I prohibit all the VMAs, which contain on of flags: VM_HUGETLB|VM_DONTEXPAND|VM_PFNMAP|VM_IO.
I'll check carefully, whether it's enough for vDSO.
Thanks,
Kirill
