Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patil, Kiran <kiran.patil@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH V0] i40e: Program device correctly as part of adding flow director entry
Date: Tue, 2 Aug 2016 12:16:21 -0700	[thread overview]
Message-ID: <57A0F185.1040208@intel.com> (raw)
In-Reply-To: <57A0E585.7090709@gmail.com>

On 8/2/2016 11:25 AM, John Fastabend wrote:
> On 16-07-27 08:52 AM, Wyborny, Carolyn wrote:
>>> -----Original Message-----
>>> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuosl.org] On
>>> Behalf Of Jeff Kirsher
>>> Sent: Tuesday, July 26, 2016 11:02 PM
>>> To: Patil, Kiran <kiran.patil@intel.com>; intel-wired-lan at lists.osuosl.org;
>>> Bowers, AndrewX <andrewx.bowers@intel.com>
>>> Subject: Re: [Intel-wired-lan] [PATCH V0] i40e: Program device correctly as part
>>> of adding flow director entry
>>>
>>> On Tue, 2016-07-26 at 22:49 -0700, Kiran Patil wrote:
>>>> This patch fixes the problem where driver was not programming
>>>> underlying device correctly when user specifies less than full tuple
>>>> set as part of adding flow director entry (for flow-type tcp4/udp4)
>>>> using ethtool.
>>>>
>>>> Signed-off-by: Kiran Patil <kiran.patil@intel.com>
>>>> Change-Id: I90052508f8c172c0da5a4b78b949704b4a59ea78
>>>> Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
>>>> ---
>>>>   drivers/net/ethernet/intel/i40e/i40e_ethtool.c | 116
>>>> +++++++++++++++++++++++++
>>>>   1 file changed, 116 insertions(+)
>>>
>>> Andrew, I know your tested-by is already on this, but I also know it was
>>> not tested while in my dev-queue branch of my next-queue tree.  Can you
>>> please verify this patch in my tree?  No need to send another tested-by,
>>> just let me know if your tested-by still stands.
>>
>> Please drop this patch. The i40e team is redesigning this feature
>> with a couple of others and it will be submitted at a future time.
>>
>> Thanks,
>>
>> Carolyn
>> _____________
>
> But wasn't this a bugfix? Shouldn't the bug fix go out now or can I
> expect the redesign shortly. Another thing to consider is a redesign
Redesign will address generic problem, implementation of flow-director 
(w.r.t. mask) whereas this patch is isolated and fixing the bug and it 
will still be required.
	-- Kiran
> may be harder to pull into distributions if you just wanted a simple
> fix like this.
>
> .John
>
>


  reply	other threads:[~2016-08-02 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27  5:49 [Intel-wired-lan] [PATCH V0] i40e: Program device correctly as part of adding flow director entry Kiran Patil
2016-07-27  6:01 ` Jeff Kirsher
2016-07-27 15:52   ` Wyborny, Carolyn
2016-08-02 18:25     ` John Fastabend
2016-08-02 19:16       ` Patil, Kiran [this message]
2016-07-27 15:53 ` Jeff Kirsher

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=57A0F185.1040208@intel.com \
    --to=kiran.patil@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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