netxen: separate register and memory access lock
Since register and onboard memory access has separate window registers, they need not be kept under same lock. Also, memory is always accessed from process context (mostly for firmware init and diagnostic tools). Signed-off-by: Dhananjay Phadke <dhananjay@netxen.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:

committed by
David S. Miller

parent
907fa1201c
commit
f03b0ebd8e
@@ -551,6 +551,9 @@ struct netxen_hardware_context {
|
||||
u32 ocm_win;
|
||||
u32 crb_win;
|
||||
|
||||
rwlock_t crb_lock;
|
||||
spinlock_t mem_lock;
|
||||
|
||||
u8 cut_through;
|
||||
u8 revision_id;
|
||||
u8 pci_func;
|
||||
@@ -1115,8 +1118,6 @@ struct netxen_adapter {
|
||||
struct pci_dev *pdev;
|
||||
struct list_head mac_list;
|
||||
|
||||
rwlock_t adapter_lock;
|
||||
|
||||
spinlock_t tx_clean_lock;
|
||||
|
||||
u16 num_txd;
|
||||
|
Reference in New Issue
Block a user