> That's not huge (supposing you have something like 128mbyte of phys ram).
> But as just said even if if such memory would be huge, if it's really used
> as cache for the data, the shm has to be set as SHM_LOCKED (not swappable
> out) so the shm swapout code (even if superoptimized) would have no way to
> touch it.
On the other hand it may not want to be locked. The DB engine
doesn't know how its cached data relates to anything else
the kernel is doing. If the kernel has "hotter" data it might
be best to roll out some of the DB's cached data.
Mike
--
A train stops at a train station, a bus stops at a bus station.
On my desk I have a work station...
.----------------------------------------------------------------------.
| Mike Jagdis | Internet: mailto:mike@roan.co.uk |
| Roan Technology Ltd. | |
| 54A Peach Street, Wokingham | Telephone: +44 118 989 0403 |
| RG40 1XG, ENGLAND | Fax: +44 118 989 1195 |
`----------------------------------------------------------------------'
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/