Re: [patch 4/3] cpusets: memory_spread_user interleaves over all mems_allowed

David wrote:
> -			tmp = cpuset_mems_allowed(current);
> +			tmp = *newmask;

I see this as a nice little optimization, not a change in
what the code does.  That is, *newmask happens to already
hold cpuset_mems_allowed(current), so can be used for such.

Is that right?

If so, nice tweak - thanks.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [patch 4/3] cpusets: memory_spread_user interleaves over all mems_allowed
    • From: David Rientjes <[email protected]>

• Prev by Date: Re: [patch 2/2] cpusets: add interleave_over_allowed option
• Next by Date: Re: [2.6 patch] remove mm_{ptov,vtop}()
• Previous by thread: [patch 4/3] cpusets: memory_spread_user interleaves over all mems_allowed
• Next by thread: kernel 2.6.23 CFS problem?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]