public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	Chris Wedgwood <cw@f00f.org>, Avi Kivity <avi@qumranet.com>,
	kvm@vger.kernel.org, Mark McLoughlin <markmc@redhat.com>
Subject: Re: [PATCH] Work around dhclient brokenness
Date: Tue, 19 Aug 2008 18:35:08 -0500	[thread overview]
Message-ID: <48AB58AC.7050909@us.ibm.com> (raw)
In-Reply-To: <200808191908.23665.rusty@rustcorp.com.au>

Rusty Russell wrote:
> On Tuesday 19 August 2008 15:17:08 Herbert Xu wrote:
>   
>> On Mon, Aug 18, 2008 at 10:13:55PM -0700, Chris Wedgwood wrote:
>>     
>>> CSUM2 sounds so ugly though.  Features seem to get added and never
>>> removed....  how about if this had a documented short lifetime (if it
>>> really must go in)?
>>>       
>> All we need is a simple toggle to disable checksum offload.  Every
>> NIC that offers receive checksum offload allows it to be disabled.
>> virtio shouldn't be any different.
>>
>> Resetting the NIC seems a bit over the top.
>>     
>
> Not really.  We could extend the protocol, but that's currently how feature 
> negotiation works: you can't do it while the device is live.  That seemed 
> simplest.  I learnt from Xen :)
>
> (Of course, we don't need to *disable* it, we need to *enable* it).
>   

Checksum offload enabled could be a config flag.  Then it could be 
toggled while the device is live.  Of course, you need a feature flag 
for the config flag.

Regards,

Anthony Liguori

> Cheers,
> Rusty.
>   


  parent reply	other threads:[~2008-08-19 23:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-15 19:47 [PATCH] Work around dhclient brokenness Anthony Liguori
2008-08-18 10:56 ` Avi Kivity
2008-08-18 11:01   ` Herbert Xu
2008-08-18 11:06     ` Avi Kivity
2008-08-18 11:34       ` Herbert Xu
2008-08-18 11:40         ` Avi Kivity
2008-08-18 11:44           ` Herbert Xu
2008-08-18 12:15             ` Avi Kivity
2008-08-19  0:45             ` Rusty Russell
2008-08-19  3:17               ` Chris Wedgwood
2008-08-19  4:41                 ` Rusty Russell
2008-08-19  5:13                   ` Chris Wedgwood
2008-08-19  5:17                     ` Herbert Xu
2008-08-19  5:28                       ` Chris Wedgwood
2008-08-19  9:10                         ` Rusty Russell
2008-08-19 15:05                           ` Chris Wedgwood
2008-08-25  4:01                             ` Rusty Russell
2008-08-19  9:08                       ` Rusty Russell
2008-08-19  9:56                         ` Herbert Xu
2008-08-19 11:36                           ` Rusty Russell
2008-08-19 23:35                         ` Anthony Liguori [this message]
2008-08-19  9:12               ` Avi Kivity
2008-08-19 13:42                 ` Anthony Liguori
2008-08-19 13:50                   ` Avi Kivity
2008-08-19 13:54                     ` Anthony Liguori
2008-08-19 14:00                       ` Avi Kivity
2008-08-24  8:39 ` Herbert Xu

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=48AB58AC.7050909@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=cw@f00f.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@redhat.com \
    --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