Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ia04a2f01005ec28a92cc5065ee2f3bddad27f573
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
Signed-off-by: Alberto Compagno <acompagn+fdio@cisco.com>
Change-Id: I86fa8d76b22a90aa87c6623206022057ac9f30f1
|
|
hicn-plugin
Listener list returns the list of interfaces and their ip addresses
Signed-off-by: Alberto Compagno <acompagn+fdio@cisco.com>
Change-Id: I2582cf29d4f1f60964766d47ad8d6dc64504fd62
|
|
|
|
Change-Id: I07cd4c100251c42ef32117a515e8e9e39b9c3031
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
corresponding socket is destroyed"
|
|
Change-Id: I768112c920154380a614d0c5858f50efa135903d
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
|
|
|
|
Signed-off-by: michele papalini <micpapal@cisco.com>
Change-Id: Ia23dee91776ccaa0bdf667eefc850e298f966cec
|
|
Change-Id: I6b382abe374d896c9ea1e0ef5573ba166fafec94
Signed-off-by: Alberto Compagno <acompagn+fdio@cisco.com>
|
|
|
|
socket is destroyed
Signed-off-by: Alberto Compagno <acompagn+fdio@cisco.com>
Change-Id: I09268dc5ae2ad465b4a4f68607732c0d3f48e62e
|
|
|
|
Added two new messages in the binary api:
- hicn_api_face_cons_del to delete a consumer face
- hicn_api_face_prod_del to delete a producer face
Added the corresponding commands in the vpp_api_test for debugging and testing
Reworked the cache policy structure to add a new function that flash the content store
from the content coming from the destroyed producer face. This is required since the CS
while each producer face has its own lru list. Removing only the producer face without
flushing the CS from the content coming from the producer face will lead to a segfault
in case there is a hit in the CS as the lru no longer exists and it won't be possible
to update the head of the lru.
Signed-off-by: Alberto Compagno <acompagn+fdio@cisco.com>
Change-Id: I8776c86952d50900aa504dd22aec521ed25c1dae
|
|
This patch introduces a new way of requesting manifests such that
all the segments they contain fill the current transport window.
When a manifest (M) is received, we compute
L = last_segment_requested + current_window_size.
L is therefore equal or greater than the last segment of the
current window.
Then we compare L to the suffix of the next manifest that will
be (potentially) requested.
If L > next_manifest, it means that the last segment of the window is
greater than the first segment contained in the next manifest.
Therefore we request manifests until L <= next_manifest, ie until the
manifests would cover the entire window.
If L <= next_manifest, then all the manifests that were requested
already cover the window, so there's no need to request more. However
if the next manifest immediately follows the current one (M), we still
need to request it so that the content suffix queue is correctly
updated.
Signed-off-by: Olivier Roques <olvrqs@gmail.com>
Change-Id: I71a5a0031cd783277d0aa59fd68d5d7bf64fe6ae
|
|
|
|
Signed-off-by: michele papalini <micpapal@cisco.com>
Change-Id: I538d8266912fea244505e4d2ceccef0dd9a242bc
|
|
Signed-off-by: michele papalini <micpapal@cisco.com>
Change-Id: Ifdc5d912b8687bae3da78fadb05524d78e767f5a
|
|
Change-Id: I166cb56e7376fe896d41d6d371ecb3727b7563ce
Signed-off-by: Junsu Choi <junsu.choi@samsung.com>
|
|
|
|
Change-Id: Iae19e016aae833b4bc95ff6d91d51b188f398e25
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
Change-Id: Id57873d3f4152af654f3bc27778d7015495597d7
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
Currently, interests for manifests are sent independently of the
transport protocol. When receiving a manifest, interests for next
manifests are sent until the next window would be full of data
segments.
But there is no limit on the number of interests for manifests that
can be sent. After a while, the interest input buffer in the
producer's side is full of them and cannot satisfy the requests
quickly enough. This results in a large drop of bandwidth on the
consumer side. This patch allows to limit the number of in-flight
interests for manifests.
Signed-off-by: Olivier Roques <olvrqs@gmail.com>
Change-Id: Ic497bd55fd92233e4b47b04635fb9bf75506375e
|
|
Signed-off-by: Alberto Compagno <acompagn+fdio@cisco.com>
Change-Id: I41641f6d27babaa1c413ecf2fe6eae0e499df97d
|
|
|
|
Change-Id: I6a1d93a4e6beb78741d8243fc78d6ecff77b9034
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
Change-Id: I8d504b1e83f79d028f2e7bbfacda2824076aa72f
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
|
|
|
|
Change-Id: Ieb5faf5d01e460179028eaba92170ee95cf35edf
Signed-off-by: Alberto Compagno <acompagn+fdio@cisco.com>
|
|
|
|
Michain support is important to get a netx hop in a face
whose locator is resolved in the fib through a via.
Change-Id: Id0ff1522cedd5a093f242499e310a24625a3852a
Signed-off-by: Alberto Compagno <acompagn+fdio@cisco.com>
|
|
Supported messages are add, del, get, dump, get.
Each message contains a face id and the expected message has different
fields based on the face type.
The binary api specific for ip faces is still available for compatibility
but deprecated.
Change-Id: I899c6cf31a56abd39ad287ea3128993857997fcb
Signed-off-by: Alberto Compagno <acompagn+fdio@cisco.com>
|
|
Change-Id: I1055e49c93e81105996a77c088fafd4b55fdc337
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
Change-Id: If4f75d44fc66414a4a70135de7827f5082b97112
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
|
|
entering face ignore mode
Change-Id: Id6f8cc958d3c50027475d72d80eed6b65ac0996b
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
Change-Id: I8f2287a262412bacc50f3c89756ec9fd6ce30d33
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
creation causes double free
Change-Id: I63f3ac8815611fe83e75edd283eabf4d721bdbac
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
Change-Id: Ifab987a17255e20077242888b052e312f9e4c964
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
Change-Id: I3f5e3840303265ccc3d4b864d026b63a2ccb7fdf
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
|
|
Change-Id: I332e74ebcd89798c93de50ae7a20f7af8f59f54c
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|
|
The current manifest implementation is broken:
1. ManifestIndexingManager, responsible for validating manifests and
segments and retrieving the next ones, assumes that all manifests
have the same size. This assumption affects the retrieval of next
manifests which is based on the number of segments the current
manifest contains. Therefore when a non-full manifests arrives,
the computed suffix of the next manifest is wrong and refer to a
content instead, which results in an error.
2. Manifests are used to update a suffix queue which stores all
the segments listed in manifests. This queue is used to retrieve
content sequentially via a pointer indicating the next content to
fetch. When the pointer reaches the end of the suffix queue, the
consumer stops sending interests. The correct behavior would be to
wait for a new manifest which would update the queue.
This patch fixes these two issues:
1. Issue 1 was fixed by using SuffixManifest (HICN-392). This allows
to set the capacity of a manifest at the start of the consumption
instead of checking each time the size of the current manifest and
then using that (non-constant) value to retrieve the next manifests.
2. Issue 2 was fixed by passing to ManifestIndexingManager a reference
to an object capable of calling the scheduleNextInterest function,
which is then called after a new manifest is retrieved to make sure
interests for content kept being sent. This is not an optimal solution
but rather a temporary one, until the retrieval of manifests is done
at the transport level rather than in ManifestIndexingManager.
This patch also changes the order of production: manifests are now
sent before content. To do so, contents are added into a queue until
the manifest is complete.
Signed-off-by: Olivier Roques <olvrqs@gmail.com>
Change-Id: I1a1bb92ca1cf2d3c745c1b65f6c7376f916c679b
|
|
|
|
Signed-off-by: mashemat <mhemmatp@cisco.com>
Change-Id: I6c2f65e61a2f13db8261a32482336b21f07d5e45
|
|
This patch introduces a new class, SuffixStrategy and two sub-classes,
SuffixContent and SuffixManifest which allow to independently assign
suffixes to contents and manifests respectively. The produce() function
in socket_producer.cc has also been changed to use them.
Given a strategy and an offset (and optionally the capacity of a
manifest), these classes automatically compute the correct next
suffixes for both type of data (manifest or content). This removes
the burden of having to manage suffixes for instance when producing
or when retrieving content, and could be expanded to add more
strategy in the future.
Currently the only existing strategy is "INCREMENTAL": manifests
with capacity N have a suffix multiple of N+1: 0, N+1, 2(N+1) etc.
Contents have a suffix incremented by 1 except when it conflicts
with a manifest: 1, 2, ..., N, N+2, N+3, ..., 2N+1, 2N+3...
Signed-off-by: Olivier Roques <olvrqs@gmail.com>
Change-Id: Ia7692d7325240de7bea6e38b668077042e5f8758
Signed-off-by: Alberto Compagno <acompagn+fdio@cisco.com>
|
|
|
|
Change-Id: Iaac34a53ae95b511594a5dcd6b1e614eba9ff135
Signed-off-by: Jordan Augé <jordan.auge+fdio@cisco.com>
|