Re: block device/VM question

Peter T. Breuer (ptb@it.uc3m.es)
Thu, 29 Aug 2002 07:45:30 +0200 (MET DST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Rusty Russell: "Re: [PATCH] list.h update (resent again)"
Next message: Lukasz Trabinski: "NMI received for unknown reason"
Previous message: Albert Cranford: "[patch] 2.4.20-pre5 DMI blacklist IBM Thinkpad in i2c/sensors"
Maybe in reply to: Peter T. Breuer: "block device/VM question"

"A month of sundays ago ptb wrote:"
> "A month of sundays ago ptb wrote:"
> > "A month of sundays ago Thunder from the hill wrote:"
> > > > And for the O_DIRECT flag we seem to do alloc_kiovec(1, &f->f_iobuf).
> > >
> > > Perhaps we should go biovec here?

I've now tried opening the ram disk device O_DIRECT in 2.4.19. Same result
as on my driver: every write returns EINVAL.

How does one use O_DIRECT? It needs driver support?

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

Next message: Rusty Russell: "Re: [PATCH] list.h update (resent again)"
Next message: Lukasz Trabinski: "NMI received for unknown reason"
Previous message: Albert Cranford: "[patch] 2.4.20-pre5 DMI blacklist IBM Thinkpad in i2c/sensors"
Maybe in reply to: Peter T. Breuer: "block device/VM question"