[lkml]   [2006]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: CD writing in future Linux (stirring up a hornets' nest)
On Mon, Jan 30, 2006 at 05:15:20PM +0100, Joerg Schilling wrote:
> > Nothing but SPI (parallel scsi) has a target id. Everything that broadly
> > falls under SAM has luns. Because SPI is dying transport the scsi
> > midlayer will get rid of having a mandatory target id mid-term. Relying
> > on the target id to have any useful meaning is dangerous, it doesn't
> > have a really useful meaning on anything but SPI.
> And now please tell me how you believe this will be inplemented.....

There's very little places left that need to know about the target id.
A few month ago we had a detailed list on linux-scsi, but off my head these

- sdev_printk prints the device identifier which right now includes the
target id. this will become a transport class callout so the transport
can print transport-specific information
- various scanning interfaces (scsi_scan_host_selected, scsi_scan_target,
scsi_add_device) require a channel id. scsi_scan_target will lose the
id parameter because it doesn't even need it, the others will move out
of the core into the spi transport class or another module for all spi-like
drivers, as lots of RAID HBAs want SPI-like scanning
- starget_for_each_device does id comparims currently, but it can be changed
to iterate the targets parent devices list easily.

with those smaller bits the scsi core doesn't need to know about the
target id anymore.

now all this is rather pointless as you really love your scheme and don't
want to change anyway, so let's stop this discussion ;-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-02-04 12:19    [W:0.300 / U:1.576 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site