Tejun Heo writes:
> Hello, Rusty.
>
> On Thu, Jan 03, 2013 at 11:17:11AM +1030, Rusty Russell wrote:
>> > So, I guess this currently is caught in a place which isn't here or
>> > there. I'm pretty skeptical whether it makes sense to bother about
>> > static usages tho. Can I keep them for
Tejun Heo t...@kernel.org writes:
Hello, Rusty.
On Thu, Jan 03, 2013 at 11:17:11AM +1030, Rusty Russell wrote:
So, I guess this currently is caught in a place which isn't here or
there. I'm pretty skeptical whether it makes sense to bother about
static usages tho. Can I keep them for
cpuset_can_attach() prepare global variables cpus_attach and
cpuset_attach_nodemask_{to|from} which are used by cpuset_attach().
There is no reason to prepare in cpuset_can_attach(). The same
information can be accessed from cpuset_attach().
Move the prepartion logic from cpuset_can_attach() to
cpuset_can_attach() prepare global variables cpus_attach and
cpuset_attach_nodemask_{to|from} which are used by cpuset_attach().
There is no reason to prepare in cpuset_can_attach(). The same
information can be accessed from cpuset_attach().
Move the prepartion logic from cpuset_can_attach() to
Hello, Rusty.
On Thu, Jan 03, 2013 at 11:17:11AM +1030, Rusty Russell wrote:
> > So, I guess this currently is caught in a place which isn't here or
> > there. I'm pretty skeptical whether it makes sense to bother about
> > static usages tho. Can I keep them for static ones?
>
> I didn't
Tejun Heo writes:
> Hello, Rusty.
>
> On Wed, Jan 02, 2013 at 03:12:15PM +1030, Rusty Russell wrote:
>> > Hmmm? cpumask_t can't be used for stack but other than that I don't
>> > see how it would be deprecated completely. Rusty, can you please
>> > chime in?
>>
>> The
Hello, Rusty.
On Wed, Jan 02, 2013 at 03:12:15PM +1030, Rusty Russell wrote:
> > Hmmm? cpumask_t can't be used for stack but other than that I don't
> > see how it would be deprecated completely. Rusty, can you please
> > chime in?
>
> The long-never-quite-complete-plan was for struct cpumask
Hello, Rusty.
On Wed, Jan 02, 2013 at 03:12:15PM +1030, Rusty Russell wrote:
Hmmm? cpumask_t can't be used for stack but other than that I don't
see how it would be deprecated completely. Rusty, can you please
chime in?
The long-never-quite-complete-plan was for struct cpumask to be
Tejun Heo t...@kernel.org writes:
Hello, Rusty.
On Wed, Jan 02, 2013 at 03:12:15PM +1030, Rusty Russell wrote:
Hmmm? cpumask_t can't be used for stack but other than that I don't
see how it would be deprecated completely. Rusty, can you please
chime in?
The
Hello, Rusty.
On Thu, Jan 03, 2013 at 11:17:11AM +1030, Rusty Russell wrote:
So, I guess this currently is caught in a place which isn't here or
there. I'm pretty skeptical whether it makes sense to bother about
static usages tho. Can I keep them for static ones?
I didn't realize that
Tejun Heo writes:
> (cc'ing Rusty, hi!)
>
> Hello, Li.
>
> On Wed, Dec 26, 2012 at 06:20:11PM +0800, Li Zefan wrote:
>> On 2012/11/29 5:34, Tejun Heo wrote:
>> > cpuset_can_attach() prepare global variables cpus_attach and
>> > cpuset_attach_nodemask_{to|from} which are used by cpuset_attach().
Tejun Heo t...@kernel.org writes:
(cc'ing Rusty, hi!)
Hello, Li.
On Wed, Dec 26, 2012 at 06:20:11PM +0800, Li Zefan wrote:
On 2012/11/29 5:34, Tejun Heo wrote:
cpuset_can_attach() prepare global variables cpus_attach and
cpuset_attach_nodemask_{to|from} which are used by
(cc'ing Rusty, hi!)
Hello, Li.
On Wed, Dec 26, 2012 at 06:20:11PM +0800, Li Zefan wrote:
> On 2012/11/29 5:34, Tejun Heo wrote:
> > cpuset_can_attach() prepare global variables cpus_attach and
> > cpuset_attach_nodemask_{to|from} which are used by cpuset_attach().
> > There is no reason to
On 2012/11/29 5:34, Tejun Heo wrote:
> cpuset_can_attach() prepare global variables cpus_attach and
> cpuset_attach_nodemask_{to|from} which are used by cpuset_attach().
> There is no reason to prepare in cpuset_can_attach(). The same
> information can be accessed from cpuset_attach().
>
> Move
On 2012/11/29 5:34, Tejun Heo wrote:
cpuset_can_attach() prepare global variables cpus_attach and
cpuset_attach_nodemask_{to|from} which are used by cpuset_attach().
There is no reason to prepare in cpuset_can_attach(). The same
information can be accessed from cpuset_attach().
Move the
(cc'ing Rusty, hi!)
Hello, Li.
On Wed, Dec 26, 2012 at 06:20:11PM +0800, Li Zefan wrote:
On 2012/11/29 5:34, Tejun Heo wrote:
cpuset_can_attach() prepare global variables cpus_attach and
cpuset_attach_nodemask_{to|from} which are used by cpuset_attach().
There is no reason to prepare in
cpuset_can_attach() prepare global variables cpus_attach and
cpuset_attach_nodemask_{to|from} which are used by cpuset_attach().
There is no reason to prepare in cpuset_can_attach(). The same
information can be accessed from cpuset_attach().
Move the prepartion logic from cpuset_can_attach() to
cpuset_can_attach() prepare global variables cpus_attach and
cpuset_attach_nodemask_{to|from} which are used by cpuset_attach().
There is no reason to prepare in cpuset_can_attach(). The same
information can be accessed from cpuset_attach().
Move the prepartion logic from cpuset_can_attach() to
18 matches
Mail list logo
