Hi.
On Thu, 2005-07-07 at 23:32, Pekka Enberg wrote:
> Hi Nigel,
>
> > diff -ruNp 623-generic-block-io.patch-old/kernel/power/suspend_block_io.c 623-generic-block-io.patch-new/kernel/power/suspend_block_io.c
> > --- 623-generic-block-io.patch-old/kernel/power/suspend_block_io.c 1970-01-01 10:00:00.000000000 +1000
> > +++ 623-generic-block-io.patch-new/kernel/power/suspend_block_io.c 2005-07-05 23:48:59.000000000 +1000
> > @@ -0,0 +1,817 @@
> > +struct io_info {
> > + struct bio * sys_struct;
> > + long block[PAGE_SIZE/512];
>
> Aah, but for this you should use block_size(io_info->dev) instead. No
> need to mess with sector sizes. Why is this long by the way?
> PAGE_SIZE/512 is block size in bytes.
No... it's the maximum number of blocks per page. Depending upon how
the user has set the blocksize when they created the filesystem (in the
case of filesystems), the number of blocks we use per page might be 1,
2, 4 or 8.
It's long because a sector number is stored in it.
Regards,
Nigel
> > + struct page * buffer_page;
> > + struct page * data_page;
> > + unsigned long flags;
> > + struct block_device * dev;
> > + struct list_head list;
> > + int readahead_index;
> > + struct work_struct work;
> > +};
>
> Pekka
>
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |