On Thu, 2015-07-23 at 14:53 -0700, Spencer Baugh wrote:
> From: Roland Dreier
>
> In a performance profile, taking a mutex in iscsit_increment_maxcmdsn()
> shows up very high. However taking a mutex around "sess->max_cmd_sn += 1"
> seems pretty silly: we're not serializing against other
On Thu, 2015-07-23 at 14:53 -0700, Spencer Baugh wrote:
From: Roland Dreier rol...@purestorage.com
In a performance profile, taking a mutex in iscsit_increment_maxcmdsn()
shows up very high. However taking a mutex around sess-max_cmd_sn += 1
seems pretty silly: we're not serializing against
From: Roland Dreier
In a performance profile, taking a mutex in iscsit_increment_maxcmdsn()
shows up very high. However taking a mutex around "sess->max_cmd_sn += 1"
seems pretty silly: we're not serializing against other contexts in
any useful way.
I did a quick audit and there don't appear
From: Roland Dreier rol...@purestorage.com
In a performance profile, taking a mutex in iscsit_increment_maxcmdsn()
shows up very high. However taking a mutex around sess-max_cmd_sn += 1
seems pretty silly: we're not serializing against other contexts in
any useful way.
I did a quick audit and
4 matches
Mail list logo