string size greater than page size?

[lazy]

wat will happen to a std string function like strcmp etc when the size
of the string is greater than page size of the OS?
A bigger question is how will they be even stored? (if at all they can
be stored)
My guess is that this is not an issue as I assume we can malloc like
1MB(>page size), so when we try to access it,
both the pages are brought to memory. Does malloc by default tries to
allocate in the same page? If so, how will it deal with fragmentation?

Pardon me if the question doesnt make sense.

[christian.bau]

On Apr 27, 12:03 am, lazy <[e-mail]:

wat will happen to a std string function like strcmp etc when the size
of the string is greater than page size of the OS?
A bigger question is how will they be even stored? (if at all they can
be stored)
My guess is that this is not an issue as I assume we can malloc like
1MB(>page size), so when we try to access it,
both the pages are brought to memory. Does malloc by default tries to
allocate in the same page? If so, how will it deal with fragmentation?

Pardon me if the question doesnt make sense.

The standard library functions always behave the way it is described
in the C Standard.

[Chris Dollin]

lazy wrote:

wat will happen to a std string function like strcmp etc when the size
of the string is greater than page size of the OS?

Nothing. The standard functions needn't care -- or even know -- about
things like "the page size of the OS".

A bigger question is how will they be even stored?

As a sequence of bytes.

My guess is that this is not an issue as I assume we can malloc like
1MB(>page size),

How much space one can malloc depends on the underlying implementation.
It is, however, unlikely that malloc would restrict itself to space
less than the "page size". Why should it?

so when we try to access it,
both the pages are brought to memory. Does malloc by default tries to
allocate in the same page? If so, how will it deal with fragmentation?

It doesn't have to do anything, in general. OS's that have "page sizes"
tend to go to a great deal of trouble to arrange that programs running
under them don't need to know about them: that is rather the point about
memory mapping, after all.

--
A rock is not a fact. A rock is a rock.

Hewlett-Packard Limited Cain Road, Bracknell, registered no:
registered office: Berks RG12 1HN 690597 England

[Army1987]

"lazy" <ar******@gmail.comha scritto nel messaggio
news:11**********************@c18g2000prb.googlegr oups.com...

wat will happen to a std string function like strcmp etc when the size
of the string is greater than page size of the OS?
A bigger question is how will they be even stored? (if at all they can
be stored)
My guess is that this is not an issue as I assume we can malloc like
1MB(>page size), so when we try to access it,
both the pages are brought to memory. Does malloc by default tries to
allocate in the same page? If so, how will it deal with fragmentation?

Pardon me if the question doesnt make sense.

You can't know (as far as the C programming language is concerned),
and you shouldn't care. If the malloc returns a non-null pointer,
you can use as many bytes from there on as you asked it to
allocate. You don't need to know where they are.