From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 227] Flow control mode on mac Intel Corporation I350 Gigabit Network Connection (rev 01) issues
Date: Fri, 15 Mar 2019 13:46:50 +0000 [thread overview]
Message-ID: <bug-227-3@http.bugs.dpdk.org/> (raw)
Message-ID: <20190315134650.6v6d4xhjulouEUYakwdQ7mcPBT3jDiWCvcKUkrPSR8Y@z> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=227
Bug ID: 227
Summary: Flow control mode on mac Intel Corporation I350
Gigabit Network Connection (rev 01) issues
Product: DPDK
Version: 18.11
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: Aleksey.Rogozhin@infotecs.ru
Target Milestone: ---
Hi all.
Faced with the problem of changing the flow control mode on the Intel
Corporation I350 Gigabit Network Connection (rev 01). In the following snippet,
the code that sets the flow control mode.
.....
// setup flow control
struct rte_eth_fc_conf fc_conf;
if( 0 != rte_eth_dev_flow_ctrl_get( port, &fc_conf ) )
{
printf( "cannot get flow ctrl parameters\n" );
}
else
{
printf( "current flow control mode %d\n", fc_conf.mode );
fc_conf.mode = RTE_FC_NONE;
printf( "new flow control mode %d\n", fc_conf.mode );
if( 0 != rte_eth_dev_flow_ctrl_set( port, &fc_conf ) )
{
printf( "bad flow contrl parameter\n" );
}
if( 0 != rte_eth_dev_flow_ctrl_get( port, &fc_conf ) )
{
printf( "cannot get flow ctrl parameters\n" );
}
printf( "after setup flow control mode %d\n", fc_conf.mode );
}
.....
Below is the output that was generated.
.....
current flow control mode 1
new flow control mode 0
after setup flow control mode 1
.....
From this it follows that the flow control mode has not been changed.
Also the fact that the MAC has not changed the flow control mode is confirmed
by the fact that the MAC reduces the packet transmission rate when receiving
pause frames.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-03-15 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 13:46 bugzilla [this message]
2019-03-15 13:46 ` bugzilla
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=bug-227-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).