From: Alexander Duyck <alexander.duyck@gmail.com>
To: Vlad Zolotarov <vladz@cloudius-systems.com>, netdev@vger.kernel.org
Cc: gleb@cloudius-systems.com, avi@cloudius-systems.com,
jeffrey.t.kirsher@intel.com,
Don Skidmore <donald.c.skidmore@intel.com>,
"tantilov, Emil S" <emil.s.tantilov@intel.com>
Subject: Re: [PATCH net-next v1 2/5] ixgbevf: Add a RETA query code
Date: Thu, 01 Jan 2015 10:09:45 -0800 [thread overview]
Message-ID: <54A58D69.7080706@gmail.com> (raw)
In-Reply-To: <54A44188.204@cloudius-systems.com>
On 12/31/2014 10:33 AM, Vlad Zolotarov wrote:
>
> On 12/31/14 20:00, Alexander Duyck wrote:
>> I suspect this code is badly broken as it doesn't take several things
>> into account.
>>
>> First the PF redirection table can have values outside of the range
>> supported by the VF. This is allowed as the VF can set how many bits of
>> the redirection table it actually wants to use. This is controlled via
>> the PSRTYPE register. So for example the PF can be running with 4
>> queues, and the VF can run either in single queue or as just a pair of
>> queues.
>>
>> Second you could compress this data much more tightly by taking
>> advantage of the bit widths allowed. So for everything x540 and older
>> they only use a 4 bit value per entry. That means you could
>> theoretically stuff 8 entries per u32 instead of just 4.
>
> Compression is nice but I think ethtool expects it in a certain
> format: one entry per byte. And since this patch is targeting the
> ethtool the output format should be as ethtool expects it to be and
> this is what this patch does. However I agree that masking the
> appropriate bits according to PSRTYPE is required. Good catch!
The idea of compression comes into play when you consider there is
significant latency trying to get messages across the mailbox. By
reducing the number of messages needed to get the redirection table you
should be able to significantly reduce the amount of time needed to
fetch it. The job of compressing/expanding the values is actually
pretty straight forward when you consider all that should be needed is a
simple loop to perform some shift, and, and or operations.
- Alex
next prev parent reply other threads:[~2015-01-01 18:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 9:51 [PATCH net-next v1 0/5]: ixgbevf: Allow querying VFs RSS indirection table and key Vlad Zolotarov
2014-12-31 9:51 ` [PATCH net-next v1 1/5] ixgbe: Add a RETA query command to VF-PF channel API Vlad Zolotarov
2014-12-31 9:51 ` [PATCH net-next v1 2/5] ixgbevf: Add a RETA query code Vlad Zolotarov
2014-12-31 18:00 ` Alexander Duyck
2014-12-31 18:33 ` Vlad Zolotarov
2015-01-01 18:09 ` Alexander Duyck [this message]
2015-01-02 17:49 ` Vlad Zolotarov
2014-12-31 9:51 ` [PATCH net-next v1 3/5] ixgbe: Add GET_RSS_KEY command to VF-PF channel commands set Vlad Zolotarov
2014-12-31 9:51 ` [PATCH net-next v1 4/5] ixgbevf: Add RSS Key query code Vlad Zolotarov
2014-12-31 16:28 ` Jeff Kirsher
2014-12-31 17:01 ` Vlad Zolotarov
2014-12-31 18:03 ` Vlad Zolotarov
2014-12-31 18:32 ` Jeff Kirsher
2014-12-31 18:36 ` Vlad Zolotarov
2014-12-31 9:51 ` [PATCH net-next v1 5/5] ixgbevf: Add the appropriate ethtool ops to query RSS indirection table and key Vlad Zolotarov
2014-12-31 16:01 ` [PATCH net-next v1 0/5]: ixgbevf: Allow querying VFs " Jeff Kirsher
2014-12-31 16:20 ` Vlad Zolotarov
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=54A58D69.7080706@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=avi@cloudius-systems.com \
--cc=donald.c.skidmore@intel.com \
--cc=emil.s.tantilov@intel.com \
--cc=gleb@cloudius-systems.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=vladz@cloudius-systems.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).