On Sunday 19 October 2008 02:50:22 Dan Nelson wrote:
> > But if it works in general, it may simply be that it isn't really
> > applicable to my purpose (and I should modify the reader to read
> > multiple blocks).
>
> That's my suggestion, yes. That way your program would also work when
> passed
... 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 rec
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
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 thi
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
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
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.
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, per-pro
8 matches
Mail list logo
