lkml.org 
[lkml]   [2002]   [Mar]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Question about the ide related ioctl's BLK* in 2.5.7-pre1 kernel
Roberto Nibali wrote:
>>>> AFAICS you only
>>>> addressed the i386 arch with that patch, do you want the specific arch
>>>> maintainers to clean up their part when your patch is finished?
>>>>
>>>
>>> ? There's nothing arch-specific in any of this...
>>
>>
>> And there is nothing IDE related either. The code removed
>> at the time wasn't used!
>
>
> I see. So the trick is to fix hdparm and tell it not to use ioctl(fd,
> BLKRAGET, arg). But I don't think that the BIO changes introduce a means
> for readahead control/export from/to user space? Or would this be
> something like bio_ioctl(kdev_t, unsigned int, unsigned long), which is
> actually not used anywhere, or the request queue approach used by Andrew
> Morton?
>
> The reason I was confused about the arch was that sparc64, ppc64,
> mips64, s390x and x86_64 still provide a ioctl handler for those ioctl's
> hooking up the the w_long (interestig naming concept btw) function.
>
> Am I completely off the track here, mixing things up?

No I think you are entierly on track.

BTW> It's quite propably right now, that I will just reintroduce them
myself and give them the semantics of the multi-write hardware settings,
just to fix the multi write PIO problem :-).

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:25    [W:0.063 / U:5.788 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site