From: "David S. Miller" <davem@redhat.com>
To: mingo@elte.hu
Cc: jgarzik@mandrakesoft.com, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: Updated zerocopy patch up on kernel.org
Date: Wed, 10 Jan 2001 20:33:16 -0800 [thread overview]
Message-ID: <200101110433.UAA02297@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0101111138540.981-100000@e2> (message from Ingo Molnar on Thu, 11 Jan 2001 11:41:30 +0100 (CET))
In-Reply-To: <Pine.LNX.4.30.0101111138540.981-100000@e2>
Date: Thu, 11 Jan 2001 11:41:30 +0100 (CET)
From: Ingo Molnar <mingo@elte.hu>
On Tue, 9 Jan 2001, David S. Miller wrote:
> I'm actually considering making the SG w/o hwcsum situation illegal.
i believe it might still make some limited sense for normal sendmsg()
and higher MTUs (or 8k NFS) - we could copy & checksum stuff into the
->tcp_page if SG is possible and thus the SG capability improves the VM.
(because we can allocate at PAGE_SIZE granularity.)
Basically what your advocating for is to take advantage of SG-only
devices when we have full control of the page contents.
Sure this would work.
But honestly the real gain from SG-only devices would be (as you know)
the memory usage savings when sending a single static file object to
several thousand clients.
Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-11 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 1:23 Jeff Garzik
2001-01-10 0:55 ` David S. Miller
2001-01-10 1:20 ` David S. Miller
2001-01-11 10:41 ` Ingo Molnar
2001-01-11 4:33 ` David S. Miller [this message]
2001-01-11 10:38 ` Ingo Molnar
2001-01-11 12:47 ` Andrew Morton
2001-01-13 6:46 ` 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=200101110433.UAA02297@pizda.ninka.net \
--to=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@oss.sgi.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
all inboxes | Powered by JetHome®