Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264283AbTEGUHW (ORCPT ); Wed, 7 May 2003 16:07:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264284AbTEGUHW (ORCPT ); Wed, 7 May 2003 16:07:22 -0400 Received: from ns.virtualhost.dk ([195.184.98.160]:29880 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id S264283AbTEGUHT (ORCPT ); Wed, 7 May 2003 16:07:19 -0400 Date: Wed, 7 May 2003 22:19:49 +0200 From: Jens Axboe To: Bartlomiej Zolnierkiewicz Cc: Linus Torvalds , Linux Kernel Subject: Re: [PATCH] 2.5 ide 48-bit usage Message-ID: <20030507201949.GW823@suse.de> References: <20030507175033.GR823@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3449 Lines: 95 On Wed, May 07 2003, Bartlomiej Zolnierkiewicz wrote: > > On Wed, 7 May 2003, Jens Axboe wrote: > > > On Wed, May 07 2003, Linus Torvalds wrote: > > > > > > On Wed, 7 May 2003, Jens Axboe wrote: > > > > > > > > > > And testing. In particular, you might want to test whether a device > > > > > properly supports 48-bit addressing, either from the kernel or from user > > > > > programs. > > > > > > > > For that, a forced 48-bit hwif->addressing inherited by drives will > > > > suffice. And I agree, we should have that. > > > > > > No no no. > > > > > > You definitely do NOT want to set "hwif->addressing" to 1 before you've > > > tested whether it even _works_. > > > > Well duh, of course not. Whether a given request is executed in 48-bit > > or not is a check that _includes_ drive capabilities too of course. > > Yeah, we test drive capabilities properly in idedisk_setup(), > but Linus is right speaking about _hwif_ capabilities. That's a probe time item, even before drives are set up. > Jens you your patch sets hwif->rqsize to 65535 in setup-pci.c for all > PCI hwifs which is simply wrong as not all of them supports LBA48. > You should check for hwif->addressing and if true set rqsize to 65536 > (not 65535) and not in IDE PCI code but in ide_init_queue() in ide-probe.c. Yes you are right, that would be the best way of doing it. As it happens for that patch, it does not hurt or break anything. But it is certainly cleaner, I'll fix that up. > I also think that max request size should be printed for all drives, > not only 48-bit capable. Fine. > > > Imagine something like "hdparm" - other things are already in progress, > > > the system is up, and IDE commands are potentially executing concurrently. > > > What something like that wants to do is to send one request out to check > > > whether 48-bit addressing works, but it absolutely does NOT want to set > > > some interface-global flag that affects other commands. > > > > Then it just puts a taskfile request on the request queue and lets it > > reach the drive, nicely syncronized with the other requests. There's no > > need to toggle any special bits for that. > > Yes, but patch subtly breakes taskfile :-). > > Taskfile ioctl uses do_rw_taskfile() or flagged_taskfile(). > Patch replaces drive->adrressing checks by task->addressing, > but ide_taskfile_ioctl() doesn't know about it so task->addressing > will be always equal 0. Uh yes, that is wrong! > You should add checking for 48-bit commands and setting task->addressing > to 1 if neccessary to ide_taskfile_ioctl(). Right > Also changes for pdc202xx_old.c are wrong, we should check for > task->addressing not rq_lba48(rq) as taskfile requests also use this > codepath. Ok > Patch also misses updates for many uses of drive->addressing > (in ide.c, ide-io.c, icside.c, ide-tcq.c and even in ide-taskfile.c). Hmm bad grep, weird. > > > Only after it has verified that 48-bit addressing does work should it set > > > the global flag. > > > > Sounds fine. > > Jens, I like the general idea of the patch, but it needs some more work. > Linus, please don't apply for now. Agree, I'll update the patch to suit your concerns tomorrow. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/