Reenable huge pages for arrow host copying

[vyasr]

Description

It is unclear whether the performance gains here are entirely from huge pages themselves or whether invoking madvise with huge pages is primarily serving to trigger an eager population of the pages (huge or not). We attempted to provide alternate flags to madvise like MADV_WILLNEED and that was not sufficient to recover performance, so either huge pages themselves are doing something special or specifying huge pages is causing madvise to trigger a page migration that no other flag does. In any case, this change returns us to the performance before the switch to the C data interface, and this code is lifted straight out of our old implementation so I am comfortable making use of it and knowing that it is not problematic. We should explore further optimizations in this direction, though.

Resolves #17075.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[bdice]

Code looks fine (as it matches a previous code path). Can we add this interop to our benchmark suite?

[harrism]

Looks good.

[vyasr]

Code looks fine (as it matches a previous code path). Can we add this interop to our benchmark suite?

Yes, I'll open an issue.

[vyasr]

/merge