Jan Engelhardt <[email protected]> wrote: > > >> And if you check the amount of completely unneeded code Linux currently has > >> just to implement e.g. SG_IO in /dev/hd*, it could even _save_ space in the > >> kernel when converting to a clean SCSI based design. > > > >Please point me at that huge amount of code. Hint: there is none. > > I'm getting a grin: > > 15:46 takeshi:../drivers/ide > find . -type f -print0 | xargs -0 grep SG_IO > (no results) > > Looks like it's already non-redundant :) everything in drivers/block/scsi_ioctl.c is duplicate code and I am sure I would find more if I take some time.... Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jan Engelhardt <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Lee Revell <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jens Axboe <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- References:
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Arjan van de Ven <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Arjan van de Ven <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Joerg Schilling <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Lee Revell <[email protected]>
- CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Matthias Andree <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jan Engelhardt <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jens Axboe <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jan Engelhardt <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- Prev by Date: [PATCH/RFC] minix filesystem update to V3 for 2.4 kernels
- Next by Date: Re: [patch, lock validator] fix uidhash_lock <-> RCU deadlock
- Previous by thread: Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- Next by thread: Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- Index(es):
 |