porting howto for 2.5?

porting howto for 2.5?

[Peter T. Breuer]

OK, I'm beat for the night.

   io_request_lock disappeared. OK, so apparently I'm now supposed
   to use the queue lock.

   req->cmd is now an array. OK, so I really wanted the direction of
   the req, so I used rq_data_dir, which looks at the req->flags.
   But what are the flags for? I need space on a req to hold a
   "sequence number". Doesn't matter if it wraps. Just has to be
   valid for 10s. What is the cmd array an array OF?

   buffer heads have gone! Now there are "bio"s. Boo hoo .. just 
   when I was really getting good with buffer_head. How do I
   copy stuff to/from user space from a bio!? It seems to contain
   bio_vecs. 

Is there a 2.4-2.5 porting howto beginning to be developed somewhere?
Please?

How can one man do such damage in just one version increment :-)?

Peter

Re: porting howto for 2.5?

[Randy.Dunlap]

On Sat, 8 Dec 2001, Peter T. Breuer wrote:

| OK, I'm beat for the night.
|
|    io_request_lock disappeared. OK, so apparently I'm now supposed
|    to use the queue lock.
|
|    req->cmd is now an array. OK, so I really wanted the direction of
|    the req, so I used rq_data_dir, which looks at the req->flags.
|    But what are the flags for? I need space on a req to hold a
|    "sequence number". Doesn't matter if it wraps. Just has to be
|    valid for 10s. What is the cmd array an array OF?
|
|    buffer heads have gone! Now there are "bio"s. Boo hoo .. just
|    when I was really getting good with buffer_head. How do I
|    copy stuff to/from user space from a bio!? It seems to contain
|    bio_vecs.
|
| Is there a 2.4-2.5 porting howto beginning to be developed somewhere?
| Please?
|
| How can one man do such damage in just one version increment :-)?

Indeed.  8;}

For a start, see "http://www.osdl.org/archive/rddunlap/linux-port-25x.html".

If anyone has additions, corrections, comments, etc., please
send them.

-- 
~Randy