On 03/04/2013 02:00 PM, Nathan Zimmer wrote:
> Stephen Warren wrote at Monday, March 04, 2013 2:16 PM:
>> On 02/15/2013 01:47 PM, Nathan Zimmer wrote:
>>> I am currently tracking a hotlock reported by a customer on a large system,
>>> 512 cores. I am currently running 3.8-rc7 but the issue looks
To: Nathan Zimmer
Cc: v...@zeniv.linux.org.uk; eric.duma...@gmail.com;
linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org; Andrew Morton;
Eric W. Biederman; David Woodhouse; Alexey Dobriyan; Paul E. McKenney
Subject: Re: [PATCH v3 resend] procfs: Improve Scaling in proc
On 02/15/2013 01:47 PM
On 02/15/2013 01:47 PM, Nathan Zimmer wrote:
> I am currently tracking a hotlock reported by a customer on a large system,
> 512 cores. I am currently running 3.8-rc7 but the issue looks like it has
> been
> this way for a very long time.
> The offending lock is proc_dir_entry->pde_unload_lock.
On 02/15/2013 01:47 PM, Nathan Zimmer wrote:
I am currently tracking a hotlock reported by a customer on a large system,
512 cores. I am currently running 3.8-rc7 but the issue looks like it has
been
this way for a very long time.
The offending lock is proc_dir_entry-pde_unload_lock.
To: Nathan Zimmer
Cc: v...@zeniv.linux.org.uk; eric.duma...@gmail.com;
linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org; Andrew Morton;
Eric W. Biederman; David Woodhouse; Alexey Dobriyan; Paul E. McKenney
Subject: Re: [PATCH v3 resend] procfs: Improve Scaling in proc
On 02/15/2013 01:47 PM
On 03/04/2013 02:00 PM, Nathan Zimmer wrote:
Stephen Warren wrote at Monday, March 04, 2013 2:16 PM:
On 02/15/2013 01:47 PM, Nathan Zimmer wrote:
I am currently tracking a hotlock reported by a customer on a large system,
512 cores. I am currently running 3.8-rc7 but the issue looks like it
在 2013年2月16日星期六UTC+8上午4时49分15秒，Nathan Zimmer写道：
> I am currently tracking a hotlock reported by a customer on a large system,
>
> 512 cores. I am currently running 3.8-rc7 but the issue looks like it has
> been
>
> this way for a very long time.
>
> The offending lock is
在 2013年2月16日星期六UTC+8上午4时49分15秒，Nathan Zimmer写道：
I am currently tracking a hotlock reported by a customer on a large system,
512 cores. I am currently running 3.8-rc7 but the issue looks like it has
been
this way for a very long time.
The offending lock is
On Fri, 15 Feb 2013 17:39:38 -0600
Nathan Zimmer wrote:
> > So are all these games with local variable `llseek' still needed?
> > afaict the increment of pde_users will stabilize ->fops?
> We still are setting de->proc_fops to NULL to prevent new callers.
> Also we still have to save fops->
On 02/15/2013 04:12 PM, Andrew Morton wrote:
On Fri, 15 Feb 2013 14:47:54 -0600
Nathan Zimmer wrote:
I am currently tracking a hotlock reported by a customer on a large system,
512 cores. I am currently running 3.8-rc7 but the issue looks like it has been
this way for a very long time.
The
On Fri, 15 Feb 2013 14:47:54 -0600
Nathan Zimmer wrote:
> I am currently tracking a hotlock reported by a customer on a large system,
> 512 cores. I am currently running 3.8-rc7 but the issue looks like it has
> been
> this way for a very long time.
> The offending lock is
On Fri, 15 Feb 2013 14:47:54 -0600
Nathan Zimmer nzim...@sgi.com wrote:
I am currently tracking a hotlock reported by a customer on a large system,
512 cores. I am currently running 3.8-rc7 but the issue looks like it has
been
this way for a very long time.
The offending lock is
On 02/15/2013 04:12 PM, Andrew Morton wrote:
On Fri, 15 Feb 2013 14:47:54 -0600
Nathan Zimmer nzim...@sgi.com wrote:
I am currently tracking a hotlock reported by a customer on a large system,
512 cores. I am currently running 3.8-rc7 but the issue looks like it has been
this way for a very
On Fri, 15 Feb 2013 17:39:38 -0600
Nathan Zimmer nzim...@sgi.com wrote:
So are all these games with local variable `llseek' still needed?
afaict the increment of pde_users will stabilize -fops?
We still are setting de-proc_fops to NULL to prevent new callers.
Also we still have to save
14 matches
Mail list logo
