public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: "David S. Miller" <davem@redhat.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	anton@samba.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5.50-BK + 24 CPUs
Date: Mon, 09 Dec 2002 18:03:10 +0100	[thread overview]
Message-ID: <3DF4CCCE.7040407@colorfullife.com> (raw)
In-Reply-To: <1039389778.13079.1.camel@rth.ninka.net>

David S. Miller wrote:

>On Sun, 2002-12-08 at 13:28, William Lee Irwin III wrote:
>  
>
>>Hmm. What happened to that pipe buffer size increase patch? That sounds
>>like it might help here, but only if those things are trying to shove
>>more than 4KB through the pipe at a time.
>>    
>>
>
>You probably mean the zero-copy pipe patches, which I think really
>should go in.  The most recent version of the diffs I saw didn't
>use the zero copy bits unless the trasnfers were quite large so it
>should be ok and not pessimize small transfers.
>
>That patch has been gathering cobwebs for more than a year now when I
>first did it, let's push this in already :-)
>  
>
Unfortunately zero-copy doesn't help to avoid the schedules:
Zero copy just avoid the copy to kernel - you still need one schedule 
for each page to be transfered.

writer calls
    for(;;){
        prepare_data(buf);
        write(fd,buf,PAGE_SIZE);
    }
reader calls
    for(;;) {
        read(fd,buf,PAGE_SIZE);
        use_data(buf);
    }

What's needed is a large kernel buffer - I've seen buffers between 64 
and 256 kB in other unices.
zero copy only helps lmbench and other apps where the whole working set 
fits into the cpu cache.

The difference between
    main-mem->cache;cache->main_mem [non-zerocopy]
and
    main-mem->main-mem [zerocopy, the copy to kernel is skipped]
is small.

--
    Manfred


  parent reply	other threads:[~2002-12-09 16:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-08 21:22 2.5.50-BK + 24 CPUs Manfred Spraul
2002-12-08 21:28 ` William Lee Irwin III
2002-12-08 23:22   ` David S. Miller
2002-12-08 23:01     ` William Lee Irwin III
2002-12-09 17:03     ` Manfred Spraul [this message]
2002-12-09 20:15       ` David S. Miller
2002-12-09 21:12         ` Manfred Spraul
  -- strict thread matches above, loose matches on Subject: below --
2002-12-08 13:09 Anton Blanchard
2002-12-08 14:49 ` Rik van Riel
2002-12-08 16:45   ` Rik van Riel
2002-12-09 14:08     ` Anton Blanchard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DF4CCCE.7040407@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=anton@samba.org \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox