Hello!
> freebsd-4.0 doesn't use direct transfers for PAGE_SIZE'd pipe write()s:
> it uses MINDIRECT=8192.
I see.
> (and PIPE_BUF is 512, so 4096 was possible for
> them)
8) I see.
Thank you for patience. 8)
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
From: <[EMAIL PROTECTED]>
>
> > freebsd
>
> Very funny, the idea is borrowed from there.
>
> As you could understand your patch kills it. PAGE_SIZE is one of the
most
> frequently used transfer unit.
>
freebsd-4.0 doesn't use direct transfers for PAGE_SIZE'd pipe write()s:
it uses MINDIRECT=8192
Hello!
> freebsd
Very funny, the idea is borrowed from there.
As you could understand your patch kills it. PAGE_SIZE is one of the most
frequently used transfer unit.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
From: <[EMAIL PROTECTED]>
>
> PS BTW "all unix" is unlikely to include freebsd. 8)
>
freebsd, openbsd, netbsd, tru64, openvms - all unix versions I found
free telnet guest accounts for.
Running for cover,
Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
Hello!
> It returns immediately on all unix platforms I tested
I see. It is essential moment. PAGE_SIZE was really bad threshold value.
Sigh and alas.
Alexey
PS BTW "all unix" is unlikely to include freebsd. 8)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
From: <[EMAIL PROTECTED]>
> Hello!
>
> > * davem's patch breaks apps that assume that write(,PIPE_BUF) after
> > poll(POLLOUT) never blocks, even for blocking pipes.
>
> Pardon, but PIPE_BUF <= PAGE_SIZE yet, so that fears have no reasons.
>
The difference is the =
> < davem's patch
> +
Hello!
> * davem's patch breaks apps that assume that write(,PIPE_BUF) after
> poll(POLLOUT) never blocks, even for blocking pipes.
Pardon, but PIPE_BUF <= PAGE_SIZE yet, so that fears have no reasons.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Mon, 12 Mar 2001, Ingo Oeser wrote:
> On Mon, Mar 12, 2001 at 05:20:12PM +0100, Mike Galbraith wrote:
> > I just happen to have a 2.4.2 IKD patch sitting here, and therein
> > sits Ingo's memory leak detector... poor thing is bored to tears 8)
>
> Could to point me to mingos[1] memleak-detecto
On Mon, Mar 12, 2001 at 05:20:12PM +0100, Mike Galbraith wrote:
> I just happen to have a 2.4.2 IKD patch sitting here, and therein
> sits Ingo's memory leak detector... poor thing is bored to tears 8)
Could to point me to mingos[1] memleak-detector? I need to know,
whats going on here.
I have h
Ingo Oeser wrote:
>
> Hi Manfred,
>
> I'm running your patches [1] with sucess for a while now.
>
> Did you get any feedback about problems regarding these patches?
>
No feedback yet.
> They seem to work for me, but there seems to be a memleak in
> 2.4.x (x: 0-2), which I'm chasing down.
>
You
On Mon, 12 Mar 2001, Ingo Oeser wrote:
> They seem to work for me, but there seems to be a memleak in
> 2.4.x (x: 0-2), which I'm chasing down.
I just happen to have a 2.4.2 IKD patch sitting here, and therein
sits Ingo's memory leak detector... poor thing is bored to tears 8)
-Mike
-
Hi Manfred,
I'm running your patches [1] with sucess for a while now.
Did you get any feedback about problems regarding these patches?
They seem to work for me, but there seems to be a memleak in
2.4.x (x: 0-2), which I'm chasing down.
The problem is, it only shows up after about 3-4 days of u
12 matches
Mail list logo
