Date: Wed, 26 Sep 2012 00:46:29 -0400
From: Brad Smith b...@comstyle.com
On Sat, Jul 25, 2009 at 07:14:42AM -0400, Brad wrote:
Please test the following diff which adds flow control support
with any gem(4) adapter.
Please provide a dmesg and ifconfig gemX output.
No one ever
i exercised the vr_encap error path by setting the TX ring size to 4, and
discovered an unnecessary bus_dmamap_unload, also figured out that pointing the
ring member to an mbuf before vr_encap is committed is a bad idea. also brad
pointed out that there is no need to setup VR_MAXFRAGS *
I think this information is already given in the sentences before.
Index: mmap.2
===
RCS file: /cvs/src/lib/libc/sys/mmap.2,v
retrieving revision 1.39
diff -u -p -u -p -r1.39 mmap.2
--- mmap.2 12 Apr 2012 12:53:27 -
The FIDIC Conditions of Contract 1999
Hi Alexandre,
[...]
This change is unclear for me; AFAIU, it removes the mechanism
which makes processes wake up with a priority depending on what
they are blocked on.
[...]
Where do you see that? The code I removed/changed simply calulated the queue
from
which to remove `p` and removed
On Sat, Oct 6, 2012 at 12:40 PM, Dawe dawed...@gmx.de wrote:
I think this information is already given in the sentences before.
No, it isn't. The previous sentences say that MAP_FAILED is returned
on error; this one says that MAP_FAILED is *only* returned on error.
Contrast this to strtoul(),
