All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: "Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
	"Lobakin, Alexandr" <alexandr.lobakin@intel.com>,
	"jbrouer@redhat.com" <jbrouer@redhat.com>
Cc: brouer@redhat.com,
	"borkmann@iogearbox.net" <borkmann@iogearbox.net>,
	"Karlsson, Magnus" <magnus.karlsson@intel.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"bjorn@kernel.org" <bjorn@kernel.org>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 2/2] igc: enable XDP metadata in driver
Date: Tue, 30 Nov 2021 12:25:47 +0100	[thread overview]
Message-ID: <e462ac19-0598-5b68-eab9-93358b7e7a57@redhat.com> (raw)
In-Reply-To: <9948428f33d013105108872d51f7e6ebec21203c.camel@intel.com>



On 29/11/2021 20.03, Nguyen, Anthony L wrote:
> On Mon, 2021-11-29 at 19:13 +0100, Alexander Lobakin wrote:
>> From: Alexander Lobakin <alexandr.lobakin@intel.com>
>> Date: Mon, 29 Nov 2021 15:53:03 +0100
>>
>>> From: Jesper Dangaard Brouer <jbrouer@redhat.com>
>>> Date: Mon, 29 Nov 2021 15:39:04 +0100
>>>
>>>> On 26/11/2021 17.16, Alexander Lobakin wrote:
>>>>> From: Jesper Dangaard Brouer <brouer@redhat.com>
>>>>> Date: Mon, 15 Nov 2021 21:36:30 +0100
>>>>>
>>>>>> Enabling the XDP bpf_prog access to data_meta area is a very
>>>>>> small
>>>>>> change. Hint passing 'true' to xdp_prepare_buff().
>>
>> [ snip ]
[ snip ]
>>
>>>
>>>> Tony is it worth resending a V2 of this patch?
>>>
>>> Tony, you can take it as it is if you want, I'll correct it later
>>> in
>>> mine. Up to you.
>>
>> My "fixup" looks like (in case of v2 needed or so):
> 
> Thanks Al. If Jesper is ok with this, I'll incorporate it in before
> sending the pull request to netdev. Otherwise, you can do it as follow
> on in the other series you previously referenced.

I'm fine with you incorporating this change. Thanks! :-)
--Jesper


WARNING: multiple messages have this Message-ID (diff)
From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next 2/2] igc: enable XDP metadata in driver
Date: Tue, 30 Nov 2021 12:25:47 +0100	[thread overview]
Message-ID: <e462ac19-0598-5b68-eab9-93358b7e7a57@redhat.com> (raw)
In-Reply-To: <9948428f33d013105108872d51f7e6ebec21203c.camel@intel.com>



On 29/11/2021 20.03, Nguyen, Anthony L wrote:
> On Mon, 2021-11-29 at 19:13 +0100, Alexander Lobakin wrote:
>> From: Alexander Lobakin <alexandr.lobakin@intel.com>
>> Date: Mon, 29 Nov 2021 15:53:03 +0100
>>
>>> From: Jesper Dangaard Brouer <jbrouer@redhat.com>
>>> Date: Mon, 29 Nov 2021 15:39:04 +0100
>>>
>>>> On 26/11/2021 17.16, Alexander Lobakin wrote:
>>>>> From: Jesper Dangaard Brouer <brouer@redhat.com>
>>>>> Date: Mon, 15 Nov 2021 21:36:30 +0100
>>>>>
>>>>>> Enabling the XDP bpf_prog access to data_meta area is a very
>>>>>> small
>>>>>> change. Hint passing 'true' to xdp_prepare_buff().
>>
>> [ snip ]
[ snip ]
>>
>>>
>>>> Tony is it worth resending a V2 of this patch?
>>>
>>> Tony, you can take it as it is if you want, I'll correct it later
>>> in
>>> mine. Up to you.
>>
>> My "fixup" looks like (in case of v2 needed or so):
> 
> Thanks Al. If Jesper is ok with this, I'll incorporate it in before
> sending the pull request to netdev. Otherwise, you can do it as follow
> on in the other series you previously referenced.

I'm fine with you incorporating this change. Thanks! :-)
--Jesper


  reply	other threads:[~2021-11-30 11:25 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 20:36 [PATCH net-next 0/2] igc: driver change to support XDP metadata Jesper Dangaard Brouer
2021-11-15 20:36 ` [Intel-wired-lan] " Jesper Dangaard Brouer
2021-11-15 20:36 ` [PATCH net-next 1/2] igc: AF_XDP zero-copy metadata adjust breaks SKBs on XDP_PASS Jesper Dangaard Brouer
2021-11-15 20:36   ` [Intel-wired-lan] " Jesper Dangaard Brouer
2021-11-21 10:32   ` Kraus, NechamaX
2021-11-21 10:32     ` Kraus, NechamaX
2021-11-26 15:25   ` Maciej Fijalkowski
2021-11-26 15:25     ` Maciej Fijalkowski
2021-11-26 15:32     ` Jesper Dangaard Brouer
2021-11-26 15:32       ` Jesper Dangaard Brouer
2021-11-26 15:54       ` Alexander Lobakin
2021-11-26 15:54         ` Alexander Lobakin
2021-11-15 20:36 ` [PATCH net-next 2/2] igc: enable XDP metadata in driver Jesper Dangaard Brouer
2021-11-15 20:36   ` [Intel-wired-lan] " Jesper Dangaard Brouer
2021-11-21 10:33   ` Kraus, NechamaX
2021-11-21 10:33     ` Kraus, NechamaX
2021-11-26 16:16   ` Alexander Lobakin
2021-11-26 16:16     ` [Intel-wired-lan] " Alexander Lobakin
2021-11-29 14:39     ` Jesper Dangaard Brouer
2021-11-29 14:39       ` [Intel-wired-lan] " Jesper Dangaard Brouer
2021-11-29 14:53       ` Alexander Lobakin
2021-11-29 14:53         ` [Intel-wired-lan] " Alexander Lobakin
2021-11-29 18:13         ` Alexander Lobakin
2021-11-29 18:13           ` [Intel-wired-lan] " Alexander Lobakin
2021-11-29 19:03           ` Nguyen, Anthony L
2021-11-29 19:03             ` [Intel-wired-lan] " Nguyen, Anthony L
2021-11-30 11:25             ` Jesper Dangaard Brouer [this message]
2021-11-30 11:25               ` Jesper Dangaard Brouer
2021-11-29 14:10 ` [PATCH net-next 0/2] igc: driver change to support XDP metadata Alexander Lobakin
2021-11-29 14:10   ` [Intel-wired-lan] " Alexander Lobakin
2021-11-29 14:29   ` Jesper Dangaard Brouer
2021-11-29 14:29     ` [Intel-wired-lan] " Jesper Dangaard Brouer
2021-11-29 14:41     ` Alexander Lobakin
2021-11-29 14:41       ` [Intel-wired-lan] " Alexander Lobakin
2021-11-30 17:59 [PATCH net-next 0/2][pull request] 1GbE Intel Wired LAN Driver Updates 2021-11-30 Tony Nguyen
2021-11-30 17:59 ` [PATCH net-next 2/2] igc: enable XDP metadata in driver Tony Nguyen

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=e462ac19-0598-5b68-eab9-93358b7e7a57@redhat.com \
    --to=jbrouer@redhat.com \
    --cc=alexandr.lobakin@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=bjorn@kernel.org \
    --cc=borkmann@iogearbox.net \
    --cc=bpf@vger.kernel.org \
    --cc=brouer@redhat.com \
    --cc=davem@davemloft.net \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=kuba@kernel.org \
    --cc=magnus.karlsson@intel.com \
    --cc=netdev@vger.kernel.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 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.