2014/freebsd-arch/20140216.freebsd-arch
Messages: 24, old messages first
|
Last update: Mon Feb 13 14:14:34 2023
|
|
home | archive sorted by: subject | author | date | reverse date
1. Feb 11 John-Mark Gurney CFR: unifing sha256 userland/kernel implementation... 2. Feb 11 John Baldwin Re: core dump vs kern.ipc.shm_use_phys 3. Feb 12 John-Mark Gurney Re: CFR: unifing sha256 userland/kernel implementation... 4. Feb 12 Adrian Chadd [flowtable] don't insert a flowtable entry if the lle isn't yet valid 5. Feb 13 Michael Dexter Re: Automatic enabling of serial console 6. Feb 13 Peter Grehan Re: Automatic enabling of serial console 7. Feb 13 Adrian Chadd can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 8. Feb 14 Ryan Stone Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 9. Feb 14 Adrian Chadd Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 10. Feb 14 Adrian Chadd Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 11. Feb 14 Pawel Jakub Dawidek Re: CFR: unifing sha256 userland/kernel implementation... 12. Feb 14 John Baldwin Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 13. Feb 14 Adrian Chadd Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 14. Feb 14 John Baldwin Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 15. Feb 14 Andrey Chernov Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 16. Feb 14 John Baldwin Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 17. Feb 14 Adrian Chadd Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 18. Feb 14 Andrey Chernov Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 19. Feb 14 Adrian Chadd Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 20. Feb 14 Andrey Chernov Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?
21. Feb 15 Andriy Gapon Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 22. Feb 15 John-Mark Gurney Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 23. Feb 15 Andrey Chernov Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? 24. Feb 15 Andrey Chernov Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?
home | archive sorted by: subject | author | date | reverse date