Displaying 20 results from an estimated 67 matches for "hashtype".
Did you mean:
hashtypes
2004 Feb 26
1
ESFQ Modification
...atched/q_esfq.c
--- ./orig/q_esfq.c 2004-02-26 09:28:10.000000000 +0100
+++ ./patched/q_esfq.c 2004-01-07 22:08:04.000000000 +0100
@@ -30,7 +30,7 @@
{
fprintf(stderr, "Usage: ... esfq [ perturb SECS ] [ quantum BYTES ] [ depth FLOWS ]\n\t[ divisor HASHBITS ] [ limit PKTS ] [ hash HASHTYPE]\n");
fprintf(stderr,"Where: \n");
- fprintf(stderr,"HASHTYPE := { classic | src | dst }\n");
+ fprintf(stderr,"HASHTYPE := { classic | src | dst | fwmark }\n");
}
#define usage() return(-1)
@@ -95,6 +95,9 @@
} else...
2005 Oct 15
5
esfq ? or wrr ?
Hi
If I have a HTB class with 128kbit, and I want to
put "N" users in that class ( in order to share
bandwidth fairly ) ,
which is better for me ? esfq (hash dst) or wrr ?
I would attach esfq or wrr to HTB parent class.
Also I''ve readed on Jim script that over WRR put
a RED qdisc, but I don''t understand it.
bests
andres
2018 Jan 19
2
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...nName) looking for .debug$T and .debug$H
sections.
If you find a .debug$H section then you can just skip that object file.
If you find a .debug$T but not a .debug$H, then basically do the same thing
that LLD does in PDBLinker::mergeDebugT (create a CVTypeArray, and pass it
to GloballyHashedType::hashTypes. That will return an array of hash
values. (the format of .debug$H is the header, followed by the hash
values). Then when you're writing the list of sections, just add in the
.debug$H section right after the .debug$T section.
Currently llvm-objcopy only writes ELF files, so it would need t...
2018 Jan 28
2
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...de in lld/coff/pdb.cpp
if (Config->DebugGHashes) {
ArrayRef<GloballyHashedType> Hashes;
std::vector<GloballyHashedType> OwnedHashes;
if (Optional<ArrayRef<uint8_t>> DebugH = getDebugH(File))
Hashes = getHashesFromDebugH(*DebugH);
else {
OwnedHashes = GloballyHashedType::hashTypes(Types);
Hashes = OwnedHashes;
}
In the else block there, add a log message that says “synthesizing .debug$h
section for “ + Obj->Name
See how many of these you get. When I build chrome + all third party
libraries this way i get about 100, which is small enough to still see
large performance g...
2018 Jan 20
0
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...debug$H
> sections.
>
> If you find a .debug$H section then you can just skip that object file.
>
> If you find a .debug$T but not a .debug$H, then basically do the same
> thing that LLD does in PDBLinker::mergeDebugT (create a CVTypeArray, and
> pass it to GloballyHashedType::hashTypes. That will return an array of
> hash values. (the format of .debug$H is the header, followed by the hash
> values). Then when you're writing the list of sections, just add in the
> .debug$H section right after the .debug$T section.
>
> Currently llvm-objcopy only writes ELF f...
2018 Jan 28
0
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...onfig->DebugGHashes) {
> ArrayRef<GloballyHashedType> Hashes;
> std::vector<GloballyHashedType> OwnedHashes;
> if (Optional<ArrayRef<uint8_t>> DebugH = getDebugH(File))
> Hashes = getHashesFromDebugH(*DebugH);
> else {
> OwnedHashes = GloballyHashedType::hashTypes(Types);
> Hashes = OwnedHashes;
> }
>
> In the else block there, add a log message that says “synthesizing
> .debug$h section for “ + Obj->Name
>
> See how many of these you get. When I build chrome + all third party
> libraries this way i get about 100, which is small e...
2018 Jan 28
2
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...{
>> ArrayRef<GloballyHashedType> Hashes;
>> std::vector<GloballyHashedType> OwnedHashes;
>> if (Optional<ArrayRef<uint8_t>> DebugH = getDebugH(File))
>> Hashes = getHashesFromDebugH(*DebugH);
>> else {
>> OwnedHashes = GloballyHashedType::hashTypes(Types);
>> Hashes = OwnedHashes;
>> }
>>
>> In the else block there, add a log message that says “synthesizing
>> .debug$h section for “ + Obj->Name
>>
>> See how many of these you get. When I build chrome + all third party
>> libraries this way i...
2018 Jan 20
2
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...gt;>
>> If you find a .debug$H section then you can just skip that object file.
>>
>> If you find a .debug$T but not a .debug$H, then basically do the same
>> thing that LLD does in PDBLinker::mergeDebugT (create a CVTypeArray, and
>> pass it to GloballyHashedType::hashTypes. That will return an array of
>> hash values. (the format of .debug$H is the header, followed by the hash
>> values). Then when you're writing the list of sections, just add in the
>> .debug$H section right after the .debug$T section.
>>
>> Currently llvm-objco...
2018 Jan 20
2
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...hen you can just skip that object
>>>> file.
>>>>
>>>> If you find a .debug$T but not a .debug$H, then basically do the same
>>>> thing that LLD does in PDBLinker::mergeDebugT (create a CVTypeArray, and
>>>> pass it to GloballyHashedType::hashTypes. That will return an array of
>>>> hash values. (the format of .debug$H is the header, followed by the hash
>>>> values). Then when you're writing the list of sections, just add in the
>>>> .debug$H section right after the .debug$T section.
>>>&g...
2018 Jan 29
2
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...e> Hashes;
>>>> std::vector<GloballyHashedType> OwnedHashes;
>>>> if (Optional<ArrayRef<uint8_t>> DebugH = getDebugH(File))
>>>> Hashes = getHashesFromDebugH(*DebugH);
>>>> else {
>>>> OwnedHashes = GloballyHashedType::hashTypes(Types);
>>>> Hashes = OwnedHashes;
>>>> }
>>>>
>>>> In the else block there, add a log message that says “synthesizing
>>>> .debug$h section for “ + Obj->Name
>>>>
>>>> See how many of these you get. When I buil...
2018 Jan 20
0
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...If you find a .debug$H section then you can just skip that object file.
>>>
>>> If you find a .debug$T but not a .debug$H, then basically do the same
>>> thing that LLD does in PDBLinker::mergeDebugT (create a CVTypeArray, and
>>> pass it to GloballyHashedType::hashTypes. That will return an array of
>>> hash values. (the format of .debug$H is the header, followed by the hash
>>> values). Then when you're writing the list of sections, just add in the
>>> .debug$H section right after the .debug$T section.
>>>
>>>...
2018 Jan 29
0
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...lt;GloballyHashedType> Hashes;
>>> std::vector<GloballyHashedType> OwnedHashes;
>>> if (Optional<ArrayRef<uint8_t>> DebugH = getDebugH(File))
>>> Hashes = getHashesFromDebugH(*DebugH);
>>> else {
>>> OwnedHashes = GloballyHashedType::hashTypes(Types);
>>> Hashes = OwnedHashes;
>>> }
>>>
>>> In the else block there, add a log message that says “synthesizing
>>> .debug$h section for “ + Obj->Name
>>>
>>> See how many of these you get. When I build chrome + all third party
&...
2018 Jan 20
0
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...p that object
>>>>> file.
>>>>>
>>>>> If you find a .debug$T but not a .debug$H, then basically do the same
>>>>> thing that LLD does in PDBLinker::mergeDebugT (create a CVTypeArray, and
>>>>> pass it to GloballyHashedType::hashTypes. That will return an array of
>>>>> hash values. (the format of .debug$H is the header, followed by the hash
>>>>> values). Then when you're writing the list of sections, just add in the
>>>>> .debug$H section right after the .debug$T section.
&g...
2018 Jan 29
0
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...t;>>> std::vector<GloballyHashedType> OwnedHashes;
>>>>> if (Optional<ArrayRef<uint8_t>> DebugH = getDebugH(File))
>>>>> Hashes = getHashesFromDebugH(*DebugH);
>>>>> else {
>>>>> OwnedHashes = GloballyHashedType::hashTypes(Types);
>>>>> Hashes = OwnedHashes;
>>>>> }
>>>>>
>>>>> In the else block there, add a log message that says “synthesizing
>>>>> .debug$h section for “ + Obj->Name
>>>>>
>>>>> See how many o...
2018 Jan 20
2
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...t;>>>> file.
>>>>>>
>>>>>> If you find a .debug$T but not a .debug$H, then basically do the same
>>>>>> thing that LLD does in PDBLinker::mergeDebugT (create a CVTypeArray, and
>>>>>> pass it to GloballyHashedType::hashTypes. That will return an array
>>>>>> of hash values. (the format of .debug$H is the header, followed by the
>>>>>> hash values). Then when you're writing the list of sections, just add in
>>>>>> the .debug$H section right after the .debug$T...
2018 Jan 19
0
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
On Fri, Jan 19, 2018 at 9:44 PM, Zachary Turner <zturner at google.com> wrote:
>
>
> On Fri, Jan 19, 2018 at 12:29 PM Leonardo Santagada <santagada at gmail.com>
> wrote:
>
>> Hi,
>>
>> No I didn't, I used cl.exe from the visual studio toolchain. What I'm
>> proposing is a tool for processing .obj files in COFF format, reading them
2018 Jan 29
2
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...td::vector<GloballyHashedType> OwnedHashes;
>>>>>> if (Optional<ArrayRef<uint8_t>> DebugH = getDebugH(File))
>>>>>> Hashes = getHashesFromDebugH(*DebugH);
>>>>>> else {
>>>>>> OwnedHashes = GloballyHashedType::hashTypes(Types);
>>>>>> Hashes = OwnedHashes;
>>>>>> }
>>>>>>
>>>>>> In the else block there, add a log message that says “synthesizing
>>>>>> .debug$h section for “ + Obj->Name
>>>>>>
>>>...
2018 Jan 29
0
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...oballyHashedType> OwnedHashes;
>>>>>>> if (Optional<ArrayRef<uint8_t>> DebugH = getDebugH(File))
>>>>>>> Hashes = getHashesFromDebugH(*DebugH);
>>>>>>> else {
>>>>>>> OwnedHashes = GloballyHashedType::hashTypes(Types);
>>>>>>> Hashes = OwnedHashes;
>>>>>>> }
>>>>>>>
>>>>>>> In the else block there, add a log message that says “synthesizing
>>>>>>> .debug$h section for “ + Obj->Name
>>>>...
2018 Jan 20
0
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
...t; file.
>>>>>>>
>>>>>>> If you find a .debug$T but not a .debug$H, then basically do the
>>>>>>> same thing that LLD does in PDBLinker::mergeDebugT (create a CVTypeArray,
>>>>>>> and pass it to GloballyHashedType::hashTypes. That will return an array of
>>>>>>> hash values. (the format of .debug$H is the header, followed by the hash
>>>>>>> values). Then when you're writing the list of sections, just add in the
>>>>>>> .debug$H section right after...
2007 Nov 15
2
IPSEC help
Hi,
I am new to ipsec and trying to connect my bsd server with win 2000. I have succeeded to tunnel using pre-shared key. But regarding certificate , I failed to get success.
The following are configuration :
racoon.conf
path certificate "/usr/local/openssl/certs" ;
# "log" specifies logging level. It is followed by either "notify",