rds: Don't disable BH on BH context

Since we have already in BH context when *_write_space(),
*_data_ready() as well as *_state_change() are called, it's
unnecessary to disable BH.

Signed-off-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
Ying Xue
2012-08-19 21:44:08 +00:00
committed by David S. Miller
parent 6b923cb718
commit bfdc587c5a
4 changed files with 8 additions and 8 deletions

View File

@@ -174,7 +174,7 @@ void rds_tcp_write_space(struct sock *sk)
struct rds_connection *conn;
struct rds_tcp_connection *tc;
read_lock_bh(&sk->sk_callback_lock);
read_lock(&sk->sk_callback_lock);
conn = sk->sk_user_data;
if (!conn) {
write_space = sk->sk_write_space;
@@ -194,7 +194,7 @@ void rds_tcp_write_space(struct sock *sk)
queue_delayed_work(rds_wq, &conn->c_send_w, 0);
out:
read_unlock_bh(&sk->sk_callback_lock);
read_unlock(&sk->sk_callback_lock);
/*
* write_space is only called when data leaves tcp's send queue if