From: Shweta Choudaha <shweta.choudaha@gmail.com>
To: dev@dpdk.org
Cc: Shweta Choudaha <shweta.choudaha@att.com>
Subject: Re: [dpdk-dev] [PATCH 0/1] net/ixgbe: Add API to update SBP bit
Date: Fri, 23 Feb 2018 13:54:34 +0000 [thread overview]
Message-ID: <CAActUdciaJsemg-gF=KMD+jyukOv+1P7kunyEL1wk8U6L1jurQ@mail.gmail.com> (raw)
Hi,
Not sure why cover letter wasn’ t appended.
In some cases we require all packets (including the ones that ixgbe
considers as Rx length errors) to be received on backplane ixgbe port. The
proposed API sets the requisite SBP bit for ixgbe to receive Rx length
error packets.
If this is required more generically for all adapters, the other approach
can be to allocate a bit in ‘struct rte_eth_rxmode’ to disable
rx_length_checking on the port. Please let me know if that is preferred or
if more info is needed
Thanks,
Shweta
On Fri, Feb 23, 2018 at 11:59 AM, Shweta Choudaha <shweta.choudaha@gmail.com
> wrote:
> From: Shweta Choudaha <shweta.choudaha@att.com>
>
> --
> 2.11.0
>
>
next reply other threads:[~2018-02-23 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 13:54 Shweta Choudaha [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-23 11:59 Shweta Choudaha
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='CAActUdciaJsemg-gF=KMD+jyukOv+1P7kunyEL1wk8U6L1jurQ@mail.gmail.com' \
--to=shweta.choudaha@gmail.com \
--cc=dev@dpdk.org \
--cc=shweta.choudaha@att.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).