> On March 13, 2019, 11:55 a.m., Benjamin Mahler wrote:
> > src/common/resource_quantities.hpp
> > Line 122 (original), 114 (patched)
> > <https://reviews.apache.org/r/70062/diff/4/?file=2131638#file2131638line124>
> >
> >     I'm curious why the rename, `get` still seems like a more readable name 
> > to me:
> >     
> >     ```
> >     quantities.get("cpus")
> >     vs
> >     quantities.quantity("cpus")
> >     ```
> >     
> >     "quantity" doesn't seem to suggest the action of retrieving the value 
> > for the name?

ok, `get` sounds good to me.
I feel `get` by default carries the connotation of getting a key (given I know 
underlying is a map interface). But I think for typical users `get` is probably 
fine. I don't have a strong opinion here. Let's use `get` then.


> On March 13, 2019, 11:55 a.m., Benjamin Mahler wrote:
> > src/common/resource_quantities.cpp
> > Lines 158-159 (patched)
> > <https://reviews.apache.org/r/70062/diff/4/?file=2131639#file2131639line159>
> >
> >     Why not advance left here? The current code does this AFAICT:
> >     
> >     // Before:
> >     //                LeftIndex
> >     //                v
> >     // Left  [0, ..., b, ...]
> >     // Right [0, ..., a, ...]
> >     //                ^ RightIndex
> >     
> >     // After:
> >     //                LeftIndex
> >     //                v
> >     // Left  [0, ..., a, b, ...]
> >     // Right [0, ..., a, z, ...]
> >     //                   ^ RightIndex
> >     
> >     We insert the missing entry into left, and we know that since we moved 
> > right index forward the next loop iteration will just execute ++leftIndex. 
> > So there's no correctness issue. However, it seems a bit strange that we've 
> > essentially taken one step backwards with left index and are now pointing 
> > to the item before `b`.
> >     
> >     Logically, it seems a bit clearer to increment left since we want to 
> > stay indexed on `b` for the next iteration?
> >     
> >     // Before:
> >     //                LeftIndex
> >     //                v
> >     // Left  [0, ..., b, ...]
> >     // Right [0, ..., a, ...]
> >     //                ^ RightIndex
> >     
> >     // After:
> >     //                   LeftIndex
> >     //                   v
> >     // Left  [0, ..., a, b, ...]
> >     // Right [0, ..., a, z, ...]
> >     //                   ^ RightIndex

Yeah, let's advance here. Thanks!


> On March 13, 2019, 11:55 a.m., Benjamin Mahler wrote:
> > src/common/resource_quantities.cpp
> > Lines 168-174 (patched)
> > <https://reviews.apache.org/r/70062/diff/4/?file=2131639#file2131639line169>
> >
> >     Might read a bit more consistent and succinct like this?
> >     
> >     ```
> >       // Copy the remaining items in `right`.
> >       while (rightIndex < right.size()) {
> >         quantities.push_back(right.quantities.at(rightIndex));
> >         ++rightIndex;
> >       }
> >     ```
> >     
> >     Basically just "finishing" the loop above for the right index.

Sounds good.


> On March 13, 2019, 11:55 a.m., Benjamin Mahler wrote:
> > src/common/resource_quantities.cpp
> > Lines 217 (patched)
> > <https://reviews.apache.org/r/70062/diff/4/?file=2131639#file2131639line218>
> >
> >     Any thoughts on CHECKing > 0 or >= 0 vs no CHECK?

I checked `>= 0`. Let's just drop the zero here.


- Meng


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/70062/#review213672
-----------------------------------------------------------


On March 14, 2019, 4:53 p.m., Meng Zhu wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70062/
> -----------------------------------------------------------
> 
> (Updated March 14, 2019, 4:53 p.m.)
> 
> 
> Review request for mesos and Benjamin Mahler.
> 
> 
> Bugs: MESOS-9608
>     https://issues.apache.org/jira/browse/MESOS-9608
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> This patch removed the map interface of
> `class ResourceQuantities`, added a few built-in
> arithmetic operations. Now, absent resource items imply
> there is no (zero) such resources.
> 
> Also added a to-do to add `class ResourceLimits` which
> is similar but treats absent resource entries as having
> infinite amount of such resource.
> 
> Also changed affected call sites and tests accordingly.
> 
> 
> Diffs
> -----
> 
>   src/common/resource_quantities.hpp 31ce7b98a8256173d6ad26e2f095373a01d7baae 
>   src/common/resource_quantities.cpp 1c8eec03580abf86df4ce947c517a74b0a8e09a7 
>   src/master/allocator/sorter/drf/sorter.hpp 
> e64c9ad3520a601f7854e807ef5306d5bffc0ff8 
>   src/master/allocator/sorter/drf/sorter.cpp 
> b128df08e3c93d3d1a75c637cbed359c2cb8cda4 
>   src/master/allocator/sorter/random/sorter.hpp 
> 4f230ec740e2f80d5333c61c5b23d9a631bdb273 
>   src/master/allocator/sorter/random/sorter.cpp 
> f578ef19b4dee9cf9c7c99a8988829ecde70ed6d 
>   src/tests/resource_quantities_tests.cpp 
> 435a4949b95e9a83be73781388eb4be9c7da695b 
> 
> 
> Diff: https://reviews.apache.org/r/70062/diff/5/
> 
> 
> Testing
> -------
> 
> make check
> Dedicated tests are added in the subsequent patch.
> 
> 
> Thanks,
> 
> Meng Zhu
> 
>

Reply via email to