From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] opensm: Add support for partition enforcement types
Date: Mon, 11 Jul 2011 08:08:54 -0400 [thread overview]
Message-ID: <4E1AE7D6.9060209@dev.mellanox.co.il> (raw)
In-Reply-To: <20110710112626.GC8520-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
Hi Alex,
On 7/10/2011 7:26 AM, Alex Netes wrote:
> Hi Hal,
>
> On 14:52 Tue 05 Jul , Hal Rosenstock wrote:
>>
>> Partition enforcement types are in, out, and both.
>> Prior to this support, both was being used so that is the default.
>>
>> Signed-off-by: Hal Rosenstock <hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
>> ---
>
> Now we end up with two parameters for same functionality:
> no_part_enforce - you define whether the enforcement is disabled or enabled.
> part_enforcement_type - you define enforcement type: in/out/both.
>
> When no_part_enforce is disabled, part_enforcement_type has no meaning.
Yes.
> Don't you find it simpler if we had only one option for partition enforcement
> with 4 options: disabled/in/out/both(default)?
I didn't want to break backward compatibility with existing command line
or option file.
If we were starting from scratch, it would be one option.
-- Hal
> -- Alex
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-07-11 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 18:52 [PATCH] opensm: Add support for partition enforcement types Hal Rosenstock
[not found] ` <4E135D51.3080208-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-07-10 11:26 ` Alex Netes
[not found] ` <20110710112626.GC8520-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2011-07-11 12:08 ` Hal Rosenstock [this message]
[not found] ` <4E1AE7D6.9060209-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-07-13 14:09 ` Alex Netes
[not found] ` <20110713140942.GC17818-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2011-07-13 23:36 ` Hal Rosenstock
[not found] ` <4E1E2C0B.6060106-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-07-24 14:42 ` [PATCHv3] " Alex Netes
[not found] ` <20110724144255.GC17166-iQai9MGU/dyyaiaB+Ve85laTQe2KTcn/@public.gmane.org>
2011-07-25 16:27 ` Alex Netes
[not found] ` <20110725162755.GE17166-iQai9MGU/dyyaiaB+Ve85laTQe2KTcn/@public.gmane.org>
2011-07-25 18:14 ` Hal Rosenstock
2012-03-22 10:25 ` [PATCHv2] " Alex Netes
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=4E1AE7D6.9060209@dev.mellanox.co.il \
--to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.