From: John Fastabend <john.fastabend@gmail.com>
To: Or Gerlitz <or.gerlitz@gmail.com>
Cc: John Fastabend <john.r.fastabend@intel.com>,
Sagi Grimberg <sagig@mellanox.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
davem@davemloft.net, netdev@vger.kernel.org, amirv@mellanox.com
Subject: Re: [PATCH net-next 3/3] net/mlx4_en: Enable open-lldp DCB support
Date: Fri, 05 Apr 2013 00:52:38 -0700 [thread overview]
Message-ID: <515E82C6.9080406@gmail.com> (raw)
In-Reply-To: <CAJZOPZJgZNkABE4+40+CnmpDRHDzEY-ZZmTH3L5JyoMHJX0Cow@mail.gmail.com>
On 04/05/2013 12:15 AM, Or Gerlitz wrote:
> John Fastabend <john.fastabend@gmail.com> wrote:
>
>> Agree it doesn't work without this patch but we can fix it in user
>> space. This has the nice benefit of letting lldpad work with mlx4 on
>> older kernels. In general I think its easier to update user space then
>> the kernel for most users. I'll send you a lldpad patch in a few moments.
>
> So to be sure we're on the same page, what we should do is enhance
> mlx4_en_dcbnl_getdcbx() routine to also return DCB_CAP_DCBX_HOST and
Right I think this is a better approach in the long run.
> work with your user space patch? sounds nice, except for what happens
> if people run with older versions of lldpad..
>
Well it won't work. But on the flip side all your older drivers _will_
work with the new daemon. My working assumption is for most users its
easier to upgrade a user space pkg than a kernel. And the simpler we
can keep the kernel code the better. Oh and also if there is a bug in
user space we shouldn't fix it with kernel code.
> Or.
>
--
John Fastabend Intel Corporation
prev parent reply other threads:[~2013-04-05 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 14:26 [PATCH net-next 0/3] Mellanox Core and Ethernet driver updates 2013-04-04 Or Gerlitz
2013-04-04 14:26 ` [PATCH net-next 1/3] net/mlx4_core: Added proper description for two device capabilities Or Gerlitz
2013-04-04 14:26 ` [PATCH net-next 2/3] net/mlx4_en: Enable DCB ETS ops only when supported by the firmware Or Gerlitz
2013-04-04 14:26 ` [PATCH net-next 3/3] net/mlx4_en: Enable open-lldp DCB support Or Gerlitz
2013-04-04 15:58 ` John Fastabend
2013-04-04 16:08 ` Sagi Grimberg
2013-04-04 19:01 ` John Fastabend
2013-04-04 21:18 ` Or Gerlitz
2013-04-04 23:54 ` John Fastabend
2013-04-05 7:15 ` Or Gerlitz
2013-04-05 7:52 ` John Fastabend [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=515E82C6.9080406@gmail.com \
--to=john.fastabend@gmail.com \
--cc=amirv@mellanox.com \
--cc=davem@davemloft.net \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=or.gerlitz@gmail.com \
--cc=sagig@mellanox.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).