From: David Ahern <dsahern@gmail.com>
To: Patrisious Haddad <phaddad@nvidia.com>, Petr Machata <petrm@nvidia.com>
Cc: jgg@ziepe.ca, leon@kernel.org, stephen@networkplumber.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linuxarm@huawei.com, linux-kernel@vger.kernel.org,
huangjunxian6@hisilicon.com, michaelgur@nvidia.com
Subject: Re: [PATCH iproute2-next 2/3] rdma: Add an option to set privileged QKEY parameter
Date: Sun, 22 Oct 2023 10:48:50 -0600 [thread overview]
Message-ID: <bc9f53d2-2d40-4c7e-85fa-cb9835df9159@gmail.com> (raw)
In-Reply-To: <c7c9562a-5c6d-eec5-3255-70238a13e96c@nvidia.com>
On 10/22/23 1:41 AM, Patrisious Haddad wrote:
>
> On 10/19/2023 1:38 PM, Petr Machata wrote:
>> Patrisious Haddad <phaddad@nvidia.com> writes:
>>
>>> @@ -40,6 +45,22 @@ static int sys_show_parse_cb(const struct nlmsghdr
>>> *nlh, void *data)
>>> mode_str);
>>> }
>>> + if (tb[RDMA_NLDEV_SYS_ATTR_PRIVILEGED_QKEY_MODE]) {
>>> + const char *pqkey_str;
>>> + uint8_t pqkey_mode;
>>> +
>>> + pqkey_mode =
>>> +
>>> mnl_attr_get_u8(tb[RDMA_NLDEV_SYS_ATTR_PRIVILEGED_QKEY_MODE]);
>>> +
>>> + if (pqkey_mode < ARRAY_SIZE(privileged_qkey_str))
>>> + pqkey_str = privileged_qkey_str[pqkey_mode];
>>> + else
>>> + pqkey_str = "unknown";
>>> +
>>> + print_color_string(PRINT_ANY, COLOR_NONE, "privileged-qkey",
>>> + "privileged-qkey %s ", pqkey_str);
>>> + }
>>> +
>> Elsewhere in the file, you just use print_color_on_off(), why not here?
>
> The print_color_on_off was used for copy-on-fork which as you see has no
> set function,
>
> I was simply trying to be consistent with this file convention & style,
> whereas print_color_string was used for the other configurable value
> ("netns"), I can obviously change that if you all see it as necessary.
>
>>
>>> if (tb[RDMA_NLDEV_SYS_ATTR_COPY_ON_FORK])
>>> cof = mnl_attr_get_u8(tb[RDMA_NLDEV_SYS_ATTR_COPY_ON_FORK]);
>>> @@ -111,10 +155,25 @@ static int sys_set_netns_args(struct rd *rd)
>>> return sys_set_netns_cmd(rd, cmd);
>>> }
>>> +static int sys_set_privileged_qkey_args(struct rd *rd)
>>> +{
>>> + bool cmd;
>>> +
>>> + if (rd_no_arg(rd) || !sys_valid_privileged_qkey_cmd(rd_argv(rd))) {
>>> + pr_err("valid options are: { on | off }\n");
>>> + return -EINVAL;
>>> + }
>> This could use parse_on_off().
> You are absolutely correct, but just as well was trying to maintain same
> code style as the previous configurable value we have here, but I think
> using parse_on_off here can save us some code.
>>
>>> +
>>> + cmd = (strcmp(rd_argv(rd), "on") == 0) ? true : false;
>>> +
>>> + return sys_set_privileged_qkey_cmd(rd, cmd);
>>> +}
>>> +
>>> static int sys_set_help(struct rd *rd)
>>> {
>>> pr_out("Usage: %s system set [PARAM] value\n", rd->filename);
>>> pr_out(" system set netns { shared | exclusive }\n");
>>> + pr_out(" system set privileged-qkey { on | off }\n");
>>> return 0;
>>> }
>>> @@ -124,6 +183,7 @@ static int sys_set(struct rd *rd)
>>> { NULL, sys_set_help },
>>> { "help", sys_set_help },
>>> { "netns", sys_set_netns_args},
>>> + { "privileged-qkey", sys_set_privileged_qkey_args},
>>> { 0 }
>>> };
>> The rest of the code looks sane to me, but I'm not familiar with the
>> feature.
> If no one else has any comments soon, and these two comments are
> actually considered critical I can re-send my patches with those issues
> fixed.
tools packaged with iproute2 should use common code where possible.
next prev parent reply other threads:[~2023-10-22 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 8:21 [PATCH iproute2-next 0/3] Add support to set privileged qkey parameter Patrisious Haddad
2023-10-19 8:21 ` [PATCH iproute2-next 1/3] rdma: update uapi headers Patrisious Haddad
2023-10-19 8:21 ` [PATCH iproute2-next 2/3] rdma: Add an option to set privileged QKEY parameter Patrisious Haddad
2023-10-19 10:38 ` Petr Machata
2023-10-19 15:05 ` David Ahern
2023-10-22 7:41 ` Patrisious Haddad
2023-10-22 16:48 ` David Ahern [this message]
2023-10-23 11:24 ` Patrisious Haddad
2023-10-22 9:22 ` Patrisious Haddad
2023-10-19 8:21 ` [PATCH iproute2-next 3/3] rdma: Adjust man page for rdma system set privileged_qkey command Patrisious Haddad
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=bc9f53d2-2d40-4c7e-85fa-cb9835df9159@gmail.com \
--to=dsahern@gmail.com \
--cc=huangjunxian6@hisilicon.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=michaelgur@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=phaddad@nvidia.com \
--cc=stephen@networkplumber.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