[
https://issues.apache.org/jira/browse/TS-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133545#comment-14133545
]
ASF subversion and git services commented on TS-3070:
-----------------------------------------------------
Commit 4747fe8f7c1c4bf6db4512f9d8ba0322b570dc8a in trafficserver's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=4747fe8 ]
TS-3070: consistent span configuration across platforms
- Remove unused Span::isRaw.
- Add ink_file_is_mmappable().
- Add ink_file_get_geometry().
- Make Span geometry variables unsigned.
- Use the symbolic constant for the Linux raw device major number.
- Allow file spans to omit the size configuration parameter.
- Use a scoped file descriptor to read Span configuration.
- Consolidate span configuration so that it is the same for all
platforms. Use ink_file_get_geometry to abstrct the method of
probing block device geometry.
- Use the inode number for the disk_id of cache files so that
multiple cache files can be used.
- Remove global Store theStore. The global Store theStore is not
used for anything that matters. The cache and hostdb subsystems
have their own separate Store instances.
> consistent span configuration
> -----------------------------
>
> Key: TS-3070
> URL: https://issues.apache.org/jira/browse/TS-3070
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache, Core
> Reporter: James Peach
> Assignee: James Peach
> Fix For: 5.2.0
>
> Attachments: TS-3070.patch
>
>
> The span configuration is not consistent across platforms because the code is
> duplicated for Linux, Solaris and the BSD family. We should refactor this
> code so that cache files and directories are handled consistently and only
> the disk geometry probing is platform specific.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
