From: Or Gerlitz <or.gerlitz@gmail.com>
To: Yevgeny Petrilin <yevgenyp@mellanox.co.il>
Cc: Roland Dreier <rdreier@cisco.com>,
netdev@vger.kernel.org, tziporet@mellanox.co.il,
liranl@mellanox.co.il
Subject: Re: Re: Re: [PATCH 18/23 v3] mlx4_core: Managing common port
Date: Wed, 17 Feb 2010 14:19:03 +0200 [thread overview]
Message-ID: <15ddcffd1002170419h2b32c044r1bdb40ed4f5753c2@mail.gmail.com> (raw)
In-Reply-To: <4B7ABBE6.1010506@mellanox.co.il>
Yevgeny Petrilin <yevgenyp@mellanox.co.il> wrote:
> HW filtering, the SW configures the filter.
I understand that at some point you plan to move to HW filter, so
maybe to rephrase the
question: is this patch set applicable without the HW filter in place?
if yes, I understood you
were planning on software filtering and wondered in what level its
expected to happen.
Or.
prev parent reply other threads:[~2010-02-17 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 15:38 Re: Re: [PATCH 18/23 v3] mlx4_core: Managing common port Yevgeny Petrilin
2010-02-17 12:19 ` Or Gerlitz [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=15ddcffd1002170419h2b32c044r1bdb40ed4f5753c2@mail.gmail.com \
--to=or.gerlitz@gmail.com \
--cc=liranl@mellanox.co.il \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=tziporet@mellanox.co.il \
--cc=yevgenyp@mellanox.co.il \
/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).