From: bharath paulraj <bharathpaul@gmail.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Reg: promiscuous mode on VF
Date: Wed, 16 Mar 2016 20:59:29 +0530 [thread overview]
Message-ID: <CACfjA+mk+mj5Ujo+6zpwXpEEjk9+MeE1b9BxuHNmxKg=jrrC=w@mail.gmail.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09090343BA89@shsmsx102.ccr.corp.intel.com>
Hi Lu,
Many thanks for your response. Again I have few more queries.
If VF unicast promiscuous mode is not supported then can't we implement a
Layer 2 bridging functionality using intel virtualization technologies? Or
Is there any other way, say tweeking some hardware registers or drivers,
which may help us in implementing Layer 2 bridging.
Also I would like to know, why intel does not support unicast promiscuos
mode? It could have been optional register settings and user should have
had a previleage to set or unset it. Besides, security reasons, is there
any other big reason why Intel does not support this?
Thanks,
Bharath Paulraj
On Wed, Mar 16, 2016 at 6:15 AM, Lu, Wenzhuo <wenzhuo.lu@intel.com> wrote:
> Hi Bharath,
>
> > 2) Is the above supported for 82599 controller? If it is supported
> in the NIC,
> > please provide the steps to enable.
> Talking about 82599, VF unicast promiscuous mode is not supported. Only
> broadcast and multicast can be supported.
>
> >
> > Thanks,
> > Bharath Paulraj
>
--
Regards,
Bharath
next prev parent reply other threads:[~2016-03-16 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 9:00 bharath paulraj
2016-03-16 0:45 ` Lu, Wenzhuo
2016-03-16 15:29 ` bharath paulraj [this message]
2016-03-16 15:54 ` Lu, Wenzhuo
2016-03-16 16:04 ` Zhang, Helin
2016-03-16 16:10 ` Rose, Gregory V
2016-03-17 6:42 ` bharath paulraj
2016-03-22 6:39 ` Qiu, Michael
2016-03-22 7:33 ` bharath paulraj
2016-03-31 10:43 ` bharath paulraj
2016-04-07 10:39 ` bharath paulraj
[not found] ` <C5551D9AAB213A418B7FD5E4A6F30A0789F7706A@ORSMSX116.amr.corp.intel.com>
2016-04-08 21:06 ` Rose, Gregory V
2016-04-12 5:51 ` bharath paulraj
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='CACfjA+mk+mj5Ujo+6zpwXpEEjk9+MeE1b9BxuHNmxKg=jrrC=w@mail.gmail.com' \
--to=bharathpaul@gmail.com \
--cc=dev@dpdk.org \
--cc=wenzhuo.lu@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).