Re: [patch] scsi: use lock per host instead of per device for shared queue tag host

Ed Lin wrote:

There may possibly be some other errors. So we need a lock here.
I think the simple but reliable way to do it is just to replace
queue lock with a host lock. James pointed out that there may be
performance slow down when many devices are accessed at the
same time. But I think the major part is still on the hardware,
and a host lock is the price these kind of controllers must pay.

I agree.

Further, a host lock is (a) common across many controllers, to protect host-wide resources and (b) only limits us when the controller is CPU-limited, a very rare scenario.

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • RE: [patch] scsi: use lock per host instead of per device for shared queue tag host
    • From: "Ed Lin" <[email protected]>

• Prev by Date: [PATCH] x86_64: fix put_user for 64-bit constant
• Next by Date: Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
• Previous by thread: RE: [patch] scsi: use lock per host instead of per device for shared queue tag host
• Next by thread: [PATCH 0/1] V4L/DVB fix
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]