Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1186706
| From | Ben Maurer <bmaurer@fb.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | RE: [RFC PATCH] thread_local_abi system call: caching current CPU number (x86) |
| Date | 2015-07-17 13:00 +0200 |
| Message-ID | <pNbwZ-3cw-13@gated-at.bofh.it> (permalink) |
| References | <pMXDH-9N-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Mathieu Desnoyers wrote: > Expose a new system call allowing threads to register a userspace memory > area where to store the current CPU number. Scheduler migration sets the I really like that this approach makes it easier to add a per-thread interaction between userspace and the kernel in the future. >+ if (!tlap || t->thread_local_abi_len < >+ offsetof(struct thread_local_abi, cpu) >+ + sizeof(tlap->cpu)) Could you save a branch here by enforcing that thread_local_abi_len = 0 if thread_local_abi = null? -b-- 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/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC PATCH] thread_local_abi system call: caching current CPU number (x86) Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2015-07-16 22:10 +0200 RE: [RFC PATCH] thread_local_abi system call: caching current CPU number (x86) Ben Maurer <bmaurer@fb.com> - 2015-07-17 13:00 +0200 Re: [RFC PATCH] thread_local_abi system call: caching current CPU number (x86) Nikolay Borisov <n.borisov@siteground.com> - 2015-07-17 14:50 +0200
csiph-web