Skip site navigation (1)Skip section navigation (2)


2013/freebsd-arch/20130915.freebsd-arch

Messages: 37, old messages first
Last update: Mon Feb 13 14:14:34 2023

home | archive sorted by: subject | author | date | reverse date
  1. Sep  8 =?iso-8859-2?Q?Edward_Toma Re: New iSCSI stack.
  2. Sep  8 Slawa Olhovchenkov         Re: New iSCSI stack.
  3. Sep  8 Outback Dingo              Re: New iSCSI stack.
  4. Sep  9 John Baldwin               Re: COMPAT_32BIT oddness in rtld-elf (was: Re: /usr/lib/private)
  5. Sep 11 Outback Dingo              Re: New iSCSI stack.
  6. Sep 11 Outback Dingo              Re: New iSCSI stack.
  7. Sep 11 Outback Dingo              Re: New iSCSI stack.
  8. Sep 11 =?iso-8859-2?Q?Edward_Toma Re: New iSCSI stack.
  9. Sep 11 Dheeraj Kandula            Why do we need to acquire the current thread's lock before context switching?
 10. Sep 12 Alfred Perlstein           Re: Why do we need to acquire the current thread's lock before context switching?
 11. Sep 12 Dheeraj Kandula            Re: Why do we need to acquire the current thread's lock before context switching?
 12. Sep 12 Svatopluk Kraus            Re: Why do we need to acquire the current thread's lock before context switching?
 13. Sep 12 Dheeraj Kandula            Re: Why do we need to acquire the current thread's lock before context switching?
 14. Sep 12 Svatopluk Kraus            Re: Why do we need to acquire the current thread's lock before context switching?
 15. Sep 12 John Baldwin               Re: Why do we need to acquire the current thread's lock before context switching?
 16. Sep 12 Dheeraj Kandula            Re: Why do we need to acquire the current thread's lock before context switching?
 17. Sep 12 Dheeraj Kandula            Re: Why do we need to acquire the current thread's lock before context switching?
 18. Sep 12 Dheeraj Kandula            Re: Why do we need to acquire the current thread's lock before context switching?
 19. Sep 12 Alfred Perlstein           Re: Why do we need to acquire the current thread's lock before context switching?
 20. Sep 12 Dheeraj Kandula            Re: Why do we need to acquire the current thread's lock before context switching?


21. Sep 12 Dheeraj Kandula Re: Why do we need to acquire the current thread's lock before context switching? 22. Sep 12 John Baldwin Re: Why do we need to acquire the current thread's lock before context switching? 23. Sep 12 Dheeraj Kandula Re: Why do we need to acquire the current thread's lock before context switching? 24. Sep 13 Julian Elischer Re: Why do we need to acquire the current thread's lock before context switching? 25. Sep 13 Dheeraj Kandula Re: Why do we need to acquire the current thread's lock before context switching? 26. Sep 13 George Neville-Neil Re: Network stack changes 27. Sep 13 Rick Macklem Re: Network stack changes 28. Sep 13 Sam Fourman Jr. Re: Network stack changes 29. Sep 14 Rick Macklem Re: Network stack changes 30. Sep 14 Anuranjan Shukla IFNAMSIZ/IF_NAMESIZE change proposal 31. Sep 14 Adrian Chadd Re: Network stack changes 32. Sep 14 Warner Losh Re: IFNAMSIZ/IF_NAMESIZE change proposal 33. Sep 14 Marcel Moolenaar Re: IFNAMSIZ/IF_NAMESIZE change proposal 34. Sep 14 Luigi Rizzo Re: Network stack changes 35. Sep 14 Luigi Rizzo Re: Network stack changes 36. Sep 14 =?ISO-8859-1?Q?Olivier_Coc Re: Network stack changes 37. Sep 14 Luigi Rizzo Re: Network stack changes


home | archive sorted by: subject | author | date | reverse date