Re: [PATCH] Block layer: separate out queue-oriented ioctls



Jens Axboe <jens.axboe@xxxxxxxxxx> wrote:

This will make it possible for cdrecord and related programs to
retrieve reliably the max_sectors value, regardless of whether the
user points it to an sr or an sg device. In particular, this will
resolve Bugzilla entry #7026.

The block bits are fine with me, the sg calling point is a bit of a sore
thumb (a char driver calling into block layer ioctls) though. So the
block layer bits are certainly ok with me, if Doug acks the sg bit I'll
merge everything up.

If you care about this kind of order, you would first need to eliminate the
ability of doing low level things like SG_IO from block drivers as this is
similar low level stuff that rather belongs to low level drivers.

Any driver that allows to use low level interfaces to send RAW SCSI commands
also needs access to other lowlevel stuff like the ability to know the
max. DMA size.



Jörg

--
EMail:joerg@xxxxxxxxxxxxxxxxxxxxxxxxxxx (home) Jörg Schilling D-13353 Berlin
js@xxxxxxxxxxxxxxx (uni)
schilling@xxxxxxxxxxxxxxxxxxx (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: IOMMU and scatterlist limits
    ... But this relies on the block layer giving me more than one ... > Hi, Pierre. ... > iteration is performed by the driver or hardware. ...
    (Linux-Kernel)
  • Re: IOMMU and scatterlist limits
    ... Is it being clever because I'm compiling for a system without an IOMMU? ... Those maximum numbers are for block layer. ... exceed above limits when it passes a request downward. ... So, if you're gonna perform sg by iterating in the driver, what ...
    (Linux-Kernel)
  • Re: Intimate relations between two objects
    ... If they are essentially device drivers whose mission is to manage low level stuff like register read/modify/write, then that sort of machination needs to be thoroughly hidden. ... In that case each driver should have a getter/setter to extract/accept the data and some third party decides when that should happen. ... That third party then just invokes the extractor getter from one and passes the data packet to the setter for the other. ... because it needs private information of o. ...
    (comp.object)
  • Re: pci_map_sg() does not coalesce adjacent physical memory? x86
    ... 319Maps a scatter gather list from the block layer. ... coalesces such entries. ... Not a block driver. ... entries in a driver is a good idea. ...
    (Linux-Kernel)
  • Re: Talking to USB
    ... I have located the low level driver DLL but there is no documentation ... There is a well documented TWAIN driver, of course, but I ... I had hoped that USB has some canonical low level comms ... Of course, each device uses different commands, but I ...
    (microsoft.public.vb.syntax)