From: Yuri Benditovich <yuri.benditovich@daynix.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Yan Vugenfirer <yan@daynix.com>, Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3 1/6] virtio-net: introduce RSS and hash report features
Date: Thu, 12 Mar 2020 11:08:20 +0200 [thread overview]
Message-ID: <CAOEp5OdEAku2EZncVKVOHk++0GwMyUiNOGDA22_7S8Whcekqaw@mail.gmail.com> (raw)
In-Reply-To: <20200312042252-mutt-send-email-mst@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2017 bytes --]
On Thu, Mar 12, 2020 at 10:23 AM Michael S. Tsirkin <mst@redhat.com> wrote:
> On Thu, Mar 12, 2020 at 09:42:20AM +0200, Yuri Benditovich wrote:
> >
> >
> > On Thu, Mar 12, 2020 at 9:21 AM Michael S. Tsirkin <mst@redhat.com>
> wrote:
> >
> > On Thu, Mar 12, 2020 at 09:02:38AM +0200, Yuri Benditovich wrote:
> > > > > +#define virtio_net_config virtio_net_config_with_rss
> > > >
> > > > Do we have to? Let's just tweak code to do the right
> thing...
> > > >
> > > >
> > > > Are we going to update the virtio_net some time?
> > > > If yes, IMO makes sense to do less tweaking in the middle of
> the
> > code.
> > > > Then, upon update of virtio_net.h - easily remove all these
> defines
> > that
> > > were
> > > > added in virtio-net.c
> > >
> > > We'll update it in a month or two. But I'd be reluctant to
> merge
> > hacks
> > > since people tend to copy-paste code ...
> > >
> > >
> > > I agree that merging hacks is very bad practice.
> > > Which change is more looks like a hack: redefine the struct to its
> _real_
> > > layout or change the type of the struct in 5 places?
> >
> > Anything that would be unacceptable as a permanent solution is a
> hack.
> > In this case how about
> > virtio_net_config_rss {
> > struct virtio_net_config config;
> > /* RSS things */
> > }
> >
> >
> > No problem.
> >
> > '#define virtio_net_config virtio_net_config_with_rss ' is OK?
> >
>
> I don't think it is, macros are supposed to be all upper case.
>
Michael, just tell me please what you want:
You prefer to change everywhere ' virtio_net_config' to
'virtio_net_config_rss' and two month later to change it back?
You prefer to change everywhere ' virtio_net_config' to
'VIRTIO_NET_CONFIG' and define it according to the needs?
Something other?
>
> >
> >
> >
> > --
> > MST
> >
> >
>
>
[-- Attachment #2: Type: text/html, Size: 3217 bytes --]
next prev parent reply other threads:[~2020-03-12 9:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 12:35 [PATCH v3 0/6] reference implementation of RSS and hash report Yuri Benditovich
2020-03-11 12:35 ` [PATCH v3 1/6] virtio-net: introduce RSS and hash report features Yuri Benditovich
2020-03-11 13:46 ` Michael S. Tsirkin
2020-03-11 13:57 ` Yuri Benditovich
2020-03-11 20:19 ` Michael S. Tsirkin
2020-03-12 7:02 ` Yuri Benditovich
2020-03-12 7:21 ` Michael S. Tsirkin
2020-03-12 7:42 ` Yuri Benditovich
2020-03-12 8:23 ` Michael S. Tsirkin
2020-03-12 9:08 ` Yuri Benditovich [this message]
2020-03-12 12:39 ` Michael S. Tsirkin
2020-03-11 12:35 ` [PATCH v3 2/6] virtio-net: implement RSS configuration command Yuri Benditovich
2020-03-11 12:35 ` [PATCH v3 3/6] virtio-net: implement RX RSS processing Yuri Benditovich
2020-03-11 12:35 ` [PATCH v3 4/6] virtio-net: reference implementation of hash report Yuri Benditovich
2020-03-11 12:35 ` [PATCH v3 5/6] virtio-net: add migration support for RSS and hast report Yuri Benditovich
2020-03-11 13:47 ` Michael S. Tsirkin
2020-03-11 14:00 ` Yuri Benditovich
2020-03-11 20:20 ` Michael S. Tsirkin
2020-03-12 7:37 ` Yuri Benditovich
2020-03-12 8:22 ` Michael S. Tsirkin
2020-03-11 12:35 ` [PATCH v3 6/6] tap: allow extended virtio header with hash info Yuri Benditovich
2020-03-11 13:10 ` [PATCH v3 0/6] reference implementation of RSS and hash report no-reply
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=CAOEp5OdEAku2EZncVKVOHk++0GwMyUiNOGDA22_7S8Whcekqaw@mail.gmail.com \
--to=yuri.benditovich@daynix.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).