On Saturday 18 October 2008 19:05:26 Sam Leffler wrote:
[EMAIL PROTECTED] wrote:
Synopsis: [request] Isn't it time to enable IPsec in GENERIC?
Responsible-Changed-From-To: freebsd-bugs-freebsd-net
Responsible-Changed-By: gavin
Responsible-Changed-When: Sat Oct 18 16:55:14 UTC 2008
Max Laier wrote:
On Saturday 18 October 2008 19:05:26 Sam Leffler wrote:
[EMAIL PROTECTED] wrote:
Synopsis: [request] Isn't it time to enable IPsec in GENERIC?
Responsible-Changed-From-To: freebsd-bugs-freebsd-net
Responsible-Changed-By: gavin
Responsible-Changed-When: Sat Oct 18
Hi,
I'm working on a program that's intended to be used as a filter, as in
something | myprogram file. I'm trying it with cat and I'm seeing my
read()s return small blocks, 64 kB in size. I suppose this is because
cat writes in 64 kB blocks. So:
a) Is there a way to programatically,
In the last episode (Oct 18), Ivan Voras said:
I'm working on a program that's intended to be used as a filter, as
in something | myprogram file. I'm trying it with cat and I'm
seeing my read()s return small blocks, 64 kB in size. I suppose this
is because cat writes in 64 kB blocks. So:
Dan Nelson wrote:
In the last episode (Oct 18), Ivan Voras said:
I'm working on a program that's intended to be used as a filter, as
in something | myprogram file. I'm trying it with cat and I'm
seeing my read()s return small blocks, 64 kB in size. I suppose this
is because cat writes in 64
In the last episode (Oct 19), Ivan Voras said:
Dan Nelson wrote:
In the last episode (Oct 18), Ivan Voras said:
I'm working on a program that's intended to be used as a filter,
as in something | myprogram file. I'm trying it with cat and
I'm seeing my read()s return small blocks, 64 kB
Hi:
I have been trying to upgrade to the latest gnash on my W/S running: FreeBSD
6.3-RELEASE-p5 #3. First, I upgraded the kernel and base to the latest patch
level, then I executed a portupgrade -R gnash, and after all the
pre-requisite packages were upgraded successfully gnash itself began to
2008/10/19 Dan Nelson [EMAIL PROTECTED]:
In the last episode (Oct 19), Ivan Voras said:
Of course. But that's not the point :) From what I see (didn't look at
the code), Linux for example does some kind of internal buffering that
decouples how the reader and the writer interact. I think that
In the last episode (Oct 19), Ivan Voras said:
2008/10/19 Dan Nelson [EMAIL PROTECTED]:
In the last episode (Oct 19), Ivan Voras said:
Of course. But that's not the point :) From what I see (didn't
look at the code), Linux for example does some kind of internal
buffering that decouples
... the writer could write 1-byte buffers and
the reader will be forced to read each byte individually.
No; take a look at /sys/kern/sys_pipe.c . Depending on how much data
is in the pipe, it switches between async in-kernel buffering (8192
bytes), and direct page wiring between sender and
10 matches
Mail list logo
