netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Oeser <netdev@axxeo.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>,
	rusty@rustcorp.com.au, anthony@codemonkey.ws,
	netdev@vger.kernel.org
Subject: Re: csum offload and af_packet
Date: Tue, 12 Aug 2008 18:17:19 +0200	[thread overview]
Message-ID: <200808121817.19662.netdev@axxeo.de> (raw)
In-Reply-To: <20080812005839.GC18547@gondor.apana.org.au>

Herbert Xu schrieb:
> The only time you need this is when you have an old guest that
> you cannot modify.  If you could modify it you can always give it
> a patched DHCP client (I've alread patched dhcp-client for Xen
> so that should work properly for KVM/lguest if you're using the
> latest version).

Are you talking about modifying the KVM client image?
There may be reasons, why this is impossible or at least highly undesired.

Before virtualisation developers of embedded stuff need to seal away
their whole machines for their development and test environment 
together with sample hardware.

Now using virtualisation they can at least virtualize their development
and test environment, save lots of cost and not risking that their sealed 
away hardware will not start again, when they need to fix a critical bug 
10-20 years later.

Now try to have them change the KVM client image :-)

Extreme special case, not worth optimizing for, I know. But that special
case is a legal one like any other special case we care about now.


Best Regards

Ingo Oeser

  reply	other threads:[~2008-08-12 16:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1216899979-32532-1-git-send-email-markmc@redhat.com>
     [not found] ` <4888EC61.8050208@codemonkey.ws>
2008-08-11  7:44   ` [PATCH 0/9][RFC] KVM virtio_net performance Rusty Russell
2008-08-11  9:51     ` Herbert Xu
2008-08-11 13:50       ` csum offload and af_packet Rusty Russell
2008-08-12  0:32         ` Herbert Xu
2008-08-12  0:51           ` David Miller
2008-08-12  0:58             ` Herbert Xu
2008-08-12 16:17               ` Ingo Oeser [this message]
2008-08-12 23:37                 ` Herbert Xu
2008-08-13  0:55                   ` David Miller
2008-08-13  1:09                     ` Herbert Xu
2008-08-13  1:17                       ` David Miller
2008-08-13  1:21                         ` Herbert Xu
2008-08-13  1:25                           ` David Miller
2008-08-13  1:37                             ` Herbert Xu
2008-08-13 11:26                       ` Patrick McHardy
2008-08-17 23:08                         ` David Miller
2008-08-18  1:10                           ` Herbert Xu
2008-08-18  1:12                             ` David Miller
     [not found]                           ` <48A8CCBF.3020408@trash.net>
2008-08-18  1:15                             ` David Miller
2008-08-18  2:12                             ` David Miller
2008-08-18 11:17                               ` Patrick McHardy
2008-08-12  2:27           ` Rusty Russell

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=200808121817.19662.netdev@axxeo.de \
    --to=netdev@axxeo.de \
    --cc=anthony@codemonkey.ws \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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;
as well as URLs for NNTP newsgroup(s).