From: Keir Fraser <keir@xensource.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Keir Fraser <keir@xensource.com>,
Xen Development Mailing List <xen-devel@lists.xensource.com>
Subject: Re: RFC: [0/2] Remove netloop by lazy copying in netback
Date: Tue, 20 Mar 2007 10:22:17 +0000 [thread overview]
Message-ID: <C2256659.BD9D%keir@xensource.com> (raw)
In-Reply-To: <20070320044625.GA17463@gondor.apana.org.au>
On 20/3/07 04:46, "Herbert Xu" <herbert@gondor.apana.org.au> wrote:
> These two patches remove the need for netloop by performing the
> copying in netback and only if it is necessary. The rationale
> is that most packets will be processed without delay allowing
> them to be freed without copying at all. So instead of copying
> every packet destined to dom0 we'll only copy those that linger
> longer than a specified amount of time (currently 0.5s).
One other thought I had -- does the Linux network stack ever modify date
residing outside the main skbuff data area (i.e., data in fragments)? If it
ever does, wouldn't your delayed copy in netback potentially race such
updates? If the Linux network stack guarantees never to do such a thing,
that would be nice for us. :-)
-- Keir
next prev parent reply other threads:[~2007-03-20 10:22 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 4:46 RFC: [0/2] Remove netloop by lazy copying in netback Herbert Xu
2007-03-20 4:50 ` RFC: [1/2] [XEN] gnttab: Add new op unmap_and_replace Herbert Xu
2007-03-20 4:56 ` RFC: [2/2] [NET] back: Add lazy copying Herbert Xu
2007-03-20 7:10 ` RFC: [0/2] Remove netloop by lazy copying in netback Keir Fraser
2007-03-20 10:11 ` Herbert Xu
2007-03-20 10:18 ` Keir Fraser
2007-03-22 10:50 ` Herbert Xu
2007-03-22 15:40 ` Keir Fraser
2007-03-23 3:17 ` Herbert Xu
2007-03-23 10:32 ` Keir Fraser
2007-03-23 11:42 ` Herbert Xu
2007-03-23 11:47 ` Keir Fraser
2007-03-23 13:24 ` Ian Pratt
2007-03-23 23:07 ` Santos, Jose Renato G
2007-03-23 23:29 ` Ian Pratt
2007-03-26 23:58 ` Santos, Jose Renato G
2007-03-27 13:15 ` Ian Pratt
2007-03-25 11:41 ` Herbert Xu
2007-03-25 12:27 ` Keir Fraser
2007-03-26 2:19 ` Herbert Xu
2007-03-26 18:36 ` Keir Fraser
2007-03-26 21:08 ` Herbert Xu
2007-03-27 0:33 ` Keir Fraser
2007-03-27 0:35 ` Herbert Xu
2007-03-27 0:46 ` Keir Fraser
2007-03-27 0:45 ` Keir Fraser
2007-03-27 0:52 ` Herbert Xu
2007-03-27 1:02 ` Keir Fraser
2007-03-27 1:08 ` Herbert Xu
2007-03-27 1:17 ` Herbert Xu
2007-03-27 3:34 ` Isaku Yamahata
2007-03-27 7:36 ` Keir Fraser
2007-03-27 7:44 ` Herbert Xu
2007-03-27 8:12 ` Keir Fraser
2007-03-27 8:15 ` Herbert Xu
2007-03-27 8:15 ` Isaku Yamahata
2007-03-27 7:51 ` Keir Fraser
2007-03-27 7:53 ` Herbert Xu
2007-03-27 7:59 ` Herbert Xu
2007-03-27 8:10 ` Keir Fraser
2007-03-27 8:13 ` Herbert Xu
2007-03-27 8:31 ` Keir Fraser
2007-03-27 9:20 ` Herbert Xu
2007-03-27 9:58 ` Keir Fraser
2007-03-27 10:06 ` Herbert Xu
2007-03-27 10:17 ` Keir Fraser
2007-03-27 10:25 ` Herbert Xu
2007-03-27 10:40 ` Keir Fraser
2007-03-27 11:09 ` Herbert Xu
2007-03-27 8:03 ` Keir Fraser
2007-03-27 8:22 ` Isaku Yamahata
2007-03-27 10:15 ` Herbert Xu
2007-03-27 10:19 ` Keir Fraser
2007-03-27 11:11 ` Herbert Xu
2007-03-27 13:50 ` Keir Fraser
2007-03-27 20:46 ` Herbert Xu
2007-03-28 13:05 ` Herbert Xu
2007-03-29 6:08 ` Isaku Yamahata
2007-03-27 3:41 ` Isaku Yamahata
2007-03-27 5:45 ` Herbert Xu
2007-03-20 10:22 ` Keir Fraser [this message]
2007-03-20 10:27 ` Keir Fraser
2007-03-20 11:50 ` David Edmondson
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=C2256659.BD9D%keir@xensource.com \
--to=keir@xensource.com \
--cc=herbert@gondor.apana.org.au \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.