All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Charles (Chas) Williams" <ciwillia@brocade.com>, dev@dpdk.org
Cc: skhare@vmware.com
Subject: Re: [PATCH V2 0/6] some local vmxnet3 patches
Date: Wed, 28 Jun 2017 18:54:44 +0100	[thread overview]
Message-ID: <98a2775e-19ae-833e-77c6-43a95deb475c@intel.com> (raw)
In-Reply-To: <ef5e9970-99a9-2787-010d-b355a2b5436d@brocade.com>

On 6/28/2017 6:15 PM, Charles (Chas) Williams wrote:
> 
> 
> On 06/28/2017 08:52 AM, Ferruh Yigit wrote:
>> On 6/28/2017 12:30 PM, Ferruh Yigit wrote:
>>> On 6/15/2017 1:16 PM, Charles (Chas) Williams wrote:
>>>> This series addresses some local issues with the vmxnet3 driver that
>>>> others might find of interest.
>>>>
>>>> Changes in v2:
>>>>
>>>> - net/vmxnet3: Implement retrieval of extended stats
>>>>
>>>>     .id field wasn't being filled in xstats.
>>>>
>>>> - net/vmxnet3: receive queue memory leak
>>>>
>>>>     The leak and buffer reallcation were split.  The buffer reallocation
>>>>     patch may be superceded by another commit so isn't included in this
>>>>     series while under discussion.
>>>>
>>>
>>> Series applied to dpdk-next-net/master, thanks.
>>
>> Hi Charles,
>>
>> Patches require vmxnet3.ini update, "Extended stats" and "Link status
>> event" ones I guess. I missed them to before getting patchset.
>>
>> Would you mind sending another patch to update features document?
>>
>> Thanks,
>> ferruh
>>
> 
> Curiously, the vmxnet3 already indicates that it is handling link
> status event interrupts.

You are right, this can be by mistake.

> 
> 
> ; Supported features of the 'vmxnet3' network poll mode driver.
> ;
> ; Refer to default.ini for the full list of available PMD features.
> ;
> [Features]
> Speed capabilities   = P
> Link status          = Y
> Link status event    = Y
> 

  reply	other threads:[~2017-06-28 17:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 17:55 [PATCH 1/6] net/vmxnet3: retain counters on restart Charles (Chas) Williams
2017-05-19 17:55 ` [PATCH 2/6] net/vmxnet3: Implement retrieval of extended stats Charles (Chas) Williams
2017-05-24  0:17   ` Shrikrishna Khare
2017-05-19 17:55 ` [PATCH 3/6] net/vmxnet3: Generate link-state change notifications Charles (Chas) Williams
2017-05-19 17:55 ` [PATCH 4/6] net/vmxnet3: Make vmxnet3_process_events less noisy Charles (Chas) Williams
2017-05-23 21:44   ` Shrikrishna Khare
2017-05-19 17:55 ` [PATCH 5/6] net/vmxnet3: receive queue lockup and memleak Charles (Chas) Williams
2017-06-01 12:24   ` Charles (Chas) Williams
2017-05-24 21:09 ` [PATCH 1/6] net/vmxnet3: retain counters on restart Shrikrishna Khare
2017-05-25 18:31   ` Nachi Prachanda
2017-05-25 20:27     ` Shrikrishna Khare
2017-05-25 22:08       ` Nachi Prachanda
2017-05-26 17:29         ` Shrikrishna Khare
2017-05-26 19:01           ` Nachi Prachanda
2017-05-26 17:31 ` Shrikrishna Khare
2017-06-15 12:16 ` [PATCH V2 0/6] some local vmxnet3 patches Charles (Chas) Williams
2017-06-15 12:16   ` [PATCH v2 1/6] net/vmxnet3: retain counters on restart Charles (Chas) Williams
2017-06-15 12:16   ` [PATCH v2 2/6] net/vmxnet3: Implement retrieval of extended stats Charles (Chas) Williams
2017-06-21  1:42     ` Shrikrishna Khare
2017-06-15 12:16   ` [PATCH v2 3/6] net/vmxnet3: Generate link-state change notifications Charles (Chas) Williams
2017-06-27 13:52     ` Ferruh Yigit
2017-06-15 12:16   ` [PATCH v2 4/6] net/vmxnet3: Make vmxnet3_process_events less noisy Charles (Chas) Williams
2017-06-28 11:30   ` [PATCH V2 0/6] some local vmxnet3 patches Ferruh Yigit
2017-06-28 12:52     ` Ferruh Yigit
2017-06-28 13:09       ` Charles (Chas) Williams
2017-06-28 17:15       ` Charles (Chas) Williams
2017-06-28 17:54         ` Ferruh Yigit [this message]
2017-06-15 12:17 ` [PATCH v2 5/6] net/vmxnet3: receive queue memory leak Charles (Chas) Williams
2017-06-23 23:00   ` Shrikrishna Khare
2017-06-15 12:17 ` [PATCH v2 6/6] net/vmxnet3: preserve configured MAC address Charles (Chas) Williams

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=98a2775e-19ae-833e-77c6-43a95deb475c@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=ciwillia@brocade.com \
    --cc=dev@dpdk.org \
    --cc=skhare@vmware.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.