All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Kanzenbach <kurt@linutronix.de>
To: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Cc: Vladimir Oltean <olteanv@gmail.com>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH RFC net-next] taprio: Handle short intervals and large packets
Date: Mon, 15 Mar 2021 14:55:12 +0100	[thread overview]
Message-ID: <87tupccyin.fsf@kurt> (raw)
In-Reply-To: <87wnucktw1.fsf@vcostago-mobl2.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 503 bytes --]

On Fri Mar 12 2021, Vinicius Costa Gomes wrote:
> My first worry was whether the segments had the same tstamp as their
> parent, and it seems that they do, so everything should just work with
> etf or the txtime-assisted mode.
>
> I just want to play with this patch a bit and see how it works in
> practice. But it looks good.

OK, thanks for testing. Most likely the segmentation can be skipped with
full offloading applied.

I'll also test a bit more, before sending a non-RFC version.

Thanks,
Kurt

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2021-03-15 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12  9:28 [PATCH RFC net-next] taprio: Handle short intervals and large packets Kurt Kanzenbach
2021-03-12 20:18 ` Vinicius Costa Gomes
2021-03-15 13:55   ` Kurt Kanzenbach [this message]

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=87tupccyin.fsf@kurt \
    --to=kurt@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=vinicius.gomes@intel.com \
    --cc=xiyou.wangcong@gmail.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.