aboutsummaryrefslogtreecommitdiffstats
path: root/src/vlib/physmem.h
blob: 1e053d65c0fa31579d1b8c18f36dbeb988d43843 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
/*
 * Copyright (c) 2015 Cisco and/or its affiliates.
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at:
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
/*
 * physmem.h: virtual <-> physical memory mapping for VLIB buffers
 *
 * Copyright (c) 2008 Eliot Dresselhaus
 *
 * Permission is hereby granted, free of charge, to any person obtaining
 * a copy of this software and associated documentation files (the
 * "Software"), to deal in the Software without restriction, including
 * without limitation the rights to use, copy, modify, merge, publish,
 * distribute, sublicense, and/or sell copies of the Software, and to
 * permit persons to whom the Software is furnished to do so, subject to
 * the following conditions:
 *
 * The above copyright notice and this permission notice shall be
 * included in all copies or substantial portions of the Software.
 *
 *  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
 *  EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
 *  MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
 *  NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
 *  LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
 *  OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
 *  WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 */

#ifndef included_vlib_physmem_h
#define included_vlib_physmem_h

typedef u8 vlib_physmem_region_index_t;

typedef struct
{
  vlib_physmem_region_index_t index;
  void *mem;
  uword size;
  int fd;
  u8 log2_page_size;
  u16 n_pages;
  u32 page_mask;

  void *heap;
  u32 flags;
#define VLIB_PHYSMEM_F_INIT_MHEAP (1<<0)
#define VLIB_PHYSMEM_F_FAKE (1<<2)

  u8 numa_node;
  u64 *page_table;
  u8 *name;
} vlib_physmem_region_t;



typedef struct
{
  vlib_physmem_region_t *regions;
} vlib_physmem_main_t;

#endif /* included_vlib_physmem_h */

/*
 * fd.io coding-style-patch-verification: ON
 *
 * Local Variables:
 * eval: (c-set-style "gnu")
 * End:
 */
add the Server Host Key to the list of known hosts. Type **yes** and hit enter. Git Review =========== The VPP documents use the gerrit server and git review for submitting and fetching patches. New patch ----------------- When working with new patch use the following to get your patch reviewed. Make sure you have modified the correct files with: .. code-block:: console $ git status $ git diff Then add and commit the patch. You may want to add a tag to the commit comments. For example for document only patches you should add the tag **DOCS:**. .. code-block:: console $ git add <filename> $ git commit -s -m "<*TAG*>: <*COMMIT_MESSAGE*>" $ git review If you are creating a draft, meaning you do not want your changes reviewed yet, do the following: .. code-block:: console $ git review -D After submitting a review, reset where the HEAD is pointing to with: .. code-block:: console $ git reset --hard origin/master Existing patch ----------------------- The "change number" used below is in the URL of the review. After clicking an individual review, the change number can be found in the URL at "https://gerrit.fd.io/r/#/c/<*CHANGE_NUMBER*>/" To view an existing patch: .. code-block:: console $ git review -d <change number> $ git status $ git diff .. caution:: If you have made changes and do "git review -d <change number>", your current changes will try to be stashed so that the working tree can change to the review branch you specified. If you want to make sure you don't lose your changes, clone another Gerrit repo into a new directory using the cloning steps shown in :ref:`clone-ssh`, and perform "git review -d <change number>" in this new directory. To modify an existing patch, make sure you modified the correct files, and apply the patch with: .. code-block:: console $ git review -d <change number> $ git status $ git diff $ git add <filename> $ git commit --amend $ git review When you're done viewing or modifying a branch, get back to the master branch with: .. code-block:: console $ git reset --hard origin/master $ git checkout master Resolving a Conflict -------------------------------- If a change has a conflict it should be resolved with the following:git-review -d <Gerrit change #> .. code-block:: console $ git rebase origin/master while (conflicts) <fix conflicts> $ git rebase --continue $ git review