All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Fleytman <dmitry@daynix.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	qemu-devel <qemu-devel@nongnu.org>, Ronen Hod <rhod@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	Yan Vugenfirer <yan@daynix.com>,
	Dmitry Fleytman <dfleytma@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/1 V4] virtio-net: dynamic network offloads configuration
Date: Sat, 20 Apr 2013 23:11:18 +0300	[thread overview]
Message-ID: <B34AE3CB-C2AC-42B8-B492-DF2D33476B5E@daynix.com> (raw)
In-Reply-To: <20130420170433.GB16115@redhat.com>

Spec patch already inside.

Sent from my iPad

On Apr 20, 2013, at 8:04 PM, "Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Fri, Apr 19, 2013 at 10:10:01AM +0300, Dmitry Fleytman wrote:
>> Hello All,
>> 
>> Any news regarding this patch?
>> 
>> Thanks,
>> Dmitry
> 
> Rusty could you comment on the spec change soon please?
> If you pick it up I think we can include the feature in QEMU 1.5.
> 
>> On Sun, Apr 7, 2013 at 9:34 AM, Dmitry Fleytman <dmitry@daynix.com> wrote:
>> 
>>    From: Dmitry Fleytman <dfleytma@redhat.com>
>> 
>>    This patch implements recently accepted by virtio-spec
>>    dynamic offloads configuration feature.
>>    See commit message for details.
>> 
>>    V4 changes:
>>      1. Feature definitions re-used for command bitmask
>>      2. Command data made uint64
>>      3. Commit messsages fixed
>> 
>>    Reported-by: Rusty Russell rusty@rustcorp.com.au
>> 
>>    V3 changes:
>>      1. Compat macro added
>>      2. Feature name beautification
>> 
>>    V2 changes:
>>      1. _GUEST_ added to command and feature names
>>      2. Live migration logic fixed
>> 
>>    Reported-by: Michael S. Tsirkin <mst@redhat.com>
>> 
>>    One of recently introduced Windows features (RSC)
>>    requires network driver to be able to enable and disable
>>    HW LRO offload on the fly without device reinitialization.
>> 
>>    Current Virtio specification doesn't support this requirement.
>>    The solution proposed by following spec patch is to add
>>    a new control command for this purpose.
>> 
>>    The same solution may be used in Linux driver for ethtool interface
>>    implementation.
>> 
>>    --
>>    1.8.1.4
>> 
>> 
>> 

  reply	other threads:[~2013-04-20 20:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1365316448-4604-1-git-send-email-dmitry@daynix.com>
2013-04-19  7:10 ` [Qemu-devel] [PATCH 0/1 V4] virtio-net: dynamic network offloads configuration Dmitry Fleytman
2013-04-20 17:04   ` Michael S. Tsirkin
2013-04-20 20:11     ` Dmitry Fleytman [this message]
2013-04-22  2:09       ` Rusty Russell
     [not found] ` <1365316448-4604-2-git-send-email-dmitry@daynix.com>
2013-04-22 17:00   ` [Qemu-devel] [PATCH 1/1 " Michael S. Tsirkin
2013-04-22 17:58     ` Anthony Liguori
2013-04-22 21:02       ` Michael S. Tsirkin
2013-05-02  5:20       ` Michael S. Tsirkin
2013-05-07  7:23         ` Dmitry Fleytman
2013-05-19 11:56       ` Michael S. Tsirkin
2013-05-19 23:40         ` Anthony Liguori
2013-04-07  6:42 [Qemu-devel] [PATCH 0/1 " Dmitry Fleytman

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=B34AE3CB-C2AC-42B8-B492-DF2D33476B5E@daynix.com \
    --to=dmitry@daynix.com \
    --cc=anthony@codemonkey.ws \
    --cc=dfleytma@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rhod@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=yan@daynix.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.