netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>
Cc: Richard Cochran <rcochran@linutronix.de>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	intel-wired-lan@lists.osuosl.org,
	Andre Guedes <andre.guedes@intel.com>,
	Anna-Maria Gleixner <anna-maria@linutronix.de>,
	David Miller <davem@davemloft.net>,
	Henrik Austad <henrik@austad.us>,
	John Stultz <john.stultz@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vinicius Costa Gomes <vinicius.gomes@intel.com>,
	"Briano, Ivan" <ivan.briano@intel.com>,
	Levi Pearson <levipearson@gmail.com>
Subject: Re: [PATCH RFC V1 net-next 0/6] Time based packet transmission
Date: Thu, 19 Oct 2017 13:44:09 -0700	[thread overview]
Message-ID: <20171019204409.vmkhii2vocum43l6@localhost> (raw)
In-Reply-To: <743a4550-7344-5e73-bf6d-6ec368263ad9@intel.com>

On Wed, Oct 18, 2017 at 03:18:55PM -0700, Jesus Sanchez-Palencia wrote:
> This is great. Just out of curiosity, were you using vlans on your tests?

No, just raw packets.  VLAN tags could be added trivially (in the
program), but that naturally avoids the kernel's VLAN code.

> I might try to reproduce them soon. I would appreciate if you could provide me
> with the scripts, please.

Ok, will do.

Thanks,
Richard

      reply	other threads:[~2017-10-19 20:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18  7:41 [PATCH RFC V1 net-next 0/6] Time based packet transmission Richard Cochran
2017-09-18  7:41 ` [PATCH RFC V1 net-next 1/6] net: Add a new socket option for a future transmit time Richard Cochran
2017-09-18 14:50   ` Richard Cochran
2017-09-18 15:18   ` Eric Dumazet
2017-09-18  7:41 ` [PATCH RFC V1 net-next 2/6] net: skbuff: Add a field to support time based transmission Richard Cochran
2017-09-18 15:14   ` Eric Dumazet
2017-09-18  7:41 ` [PATCH RFC V1 net-next 3/6] net: ipv4: raw: Hook into " Richard Cochran
2017-09-18  7:41 ` [PATCH RFC V1 net-next 4/6] net: ipv4: udp: " Richard Cochran
2017-09-18  7:41 ` [PATCH RFC V1 net-next 5/6] net: packet: " Richard Cochran
2017-09-18  7:41 ` [PATCH RFC V1 net-next 6/6] net: igb: Implement " Richard Cochran
2017-09-18 16:34 ` [PATCH RFC V1 net-next 0/6] Time based packet transmission David Miller
2017-12-05 21:22   ` Vinicius Costa Gomes
2017-09-19 14:43 ` Miroslav Lichvar
2017-09-19 16:46   ` Richard Cochran
2017-09-20 17:35 ` levipearson
2017-09-20 20:11   ` Richard Cochran
2017-10-18 22:18 ` Jesus Sanchez-Palencia
2017-10-19 20:44   ` Richard Cochran [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=20171019204409.vmkhii2vocum43l6@localhost \
    --to=richardcochran@gmail.com \
    --cc=andre.guedes@intel.com \
    --cc=anna-maria@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=henrik@austad.us \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=ivan.briano@intel.com \
    --cc=jesus.sanchez-palencia@intel.com \
    --cc=john.stultz@linaro.org \
    --cc=levipearson@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rcochran@linutronix.de \
    --cc=tglx@linutronix.de \
    --cc=vinicius.gomes@intel.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).