Hi,
On Friday, 13 January 2006 22:24, Rafael J. Wysocki wrote:
> On Friday, 13 January 2006 21:59, Pavel Machek wrote:
> > On Pá 13-01-06 21:49:38, Rafael J. Wysocki wrote:
> > > On Friday, 13 January 2006 20:53, Ingo Oeser wrote:
> > > > On Friday 13 January 2006 00:31, Rafael J. Wysocki wrote:
> > > > > On Thursday, 12 January 2006 23:09, Pavel Machek wrote:
> > > > > > > +SNAPSHOT_IOCAVAIL_SWAP - check the amount of available swap (the last argument
> > > > > > > + should be a pointer to an unsigned int variable that will contain
> > > > > > > + the result if the call is successful)
> > > > > >
> > > > > > Is this good idea? It will overflow on 32-bit systems. Ammount of
> > > > > > available swap can be >4GB. [Or maybe it is in something else than
> > > > > > bytes, then you need to specify it.]
> > > > >
> > > > > It returns the number of pages. Well, it should be written explicitly,
> > > > > so I'll fix that.
> > > >
> > > > Please always talk to the kernel in bytes. Pagesize is only a kernel
> > > > internal unit. Sth. like off64_t is fine.
> > >
> > > These are values returned by the kernel, actually. Of course I can convert them
> > > to bytes before sending to the user space, if that's preferrable.
> > >
> > > Pavel, what do you think?
> >
> > Bytes, I'd say. It would be nice if preffered image size was in bytes,
> > too, for consistency.
>
> OK
Having actually tried to do that I see two reasons for keeping the image size
in megs.
First, if that was in bytes, I'd have to pass it via a pointer, because
unsigned long might overflow on i386. Then I'd have to use get_user()
to read the value. However, afterwards I'd have to rescale that value
to megs for swsusp_shrink_memory(). It's just easier to pass the value
in megs using the last argument of ioctl() directly (which is consistent
with the /sys/power/image_size thing, BTW).
Second, if that's in bytes, it would suggest that the memory-shrinking
mechanism had byte granularity (ie. way off).
There also is a reason for which SNAPSHOT_AVAIL_SWAP should return
the number of pages, IMO. Namely, if that's in pages, the number is directly
comparable with the number of image pages which the suspending
utility can read from the image header. Otherwise it would have to rescale
one of these values using PAGE_SIZE, but that's exactly what we'd like
to avoid.
Anyway returning the swap offsets in bytes is a good idea, as it will allow us
to eliminate PAGE_SIZE from the user space utilities entirely.
Greetings,
Rafael
-
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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
