Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: "Zulkifli,
	Muhammad Husaini" <muhammad.husaini.zulkifli@intel.com>,
	"intel-wired-lan@osuosl.org" <intel-wired-lan@osuosl.org>
Cc: "pmenzel@molgen.mpg.de" <pmenzel@molgen.mpg.de>,
	"Chilakala, Mallikarjuna" <mallikarjuna.chilakala@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH v2] igc: Enhance Qbv scheduling by using first flag bit
Date: Thu, 3 Nov 2022 11:15:53 -0700	[thread overview]
Message-ID: <c3fd89e4-b87f-eee8-9c7e-f3264f01f8b3@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6180AA9E5B4C32DF523E002EB8389@SJ1PR11MB6180.namprd11.prod.outlook.com>

On 11/2/2022 6:13 PM, Zulkifli, Muhammad Husaini wrote:
>> -----Original Message-----
>> From: Nguyen, Anthony L <anthony.l.nguyen@intel.com>
>> Sent: Thursday, 3 November, 2022 5:34 AM
>> To: Zulkifli, Muhammad Husaini <muhammad.husaini.zulkifli@intel.com>;
>> intel-wired-lan@osuosl.org
>> Cc: pmenzel@molgen.mpg.de; Chilakala, Mallikarjuna
>> <mallikarjuna.chilakala@intel.com>
>> Subject: Re: [Intel-wired-lan] [PATCH v2] igc: Enhance Qbv scheduling by
>> using first flag bit
>>
>>
>>
>> On 10/25/2022 7:03 AM, Muhammad Husaini Zulkifli wrote:
>>> From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
>>>
>>> The I225 hardware has a limitation that packets can only be scheduled
>>> in the [0, cycle-time] interval. So, scheduling a packet to the start
>>> of the next cycle doesn't usually work.
>>>
>>> To overcome this, we use the Transmit Descriptor first flag to
>>> indicates that a packet should be the first packet (from a queue) in a
>>> cycle according to the section 7.5.2.9.3.4 The First Packet on Each
>>> QBV Cycle in Intel Discrete I225/6 User Manual.
>>>
>>> But this only works if there was any packet from that queue during the
>>> current cycle, to avoid this issue, we issue an empty packet if that's
>>> not the case. Also require one more descriptor to be available, to
>>> take into account the empty packet that might be issued.
>>
>> <snip>
> 
> Are you expecting me to cut the test result here?

Nothing needed here, I'm just denoting that I've cut some of the text 
out to trim the response.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2022-11-03 18:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 14:03 [Intel-wired-lan] [PATCH v2] igc: Enhance Qbv scheduling by using first flag bit Muhammad Husaini Zulkifli
2022-11-02 21:33 ` Tony Nguyen
2022-11-03  1:13   ` Zulkifli, Muhammad Husaini
2022-11-03 18:15     ` Tony Nguyen [this message]
2022-11-02 21:40 ` Tony Nguyen
2022-11-03  2:52   ` Zulkifli, Muhammad Husaini

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=c3fd89e4-b87f-eee8-9c7e-f3264f01f8b3@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    --cc=mallikarjuna.chilakala@intel.com \
    --cc=muhammad.husaini.zulkifli@intel.com \
    --cc=pmenzel@molgen.mpg.de \
    /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