Last note, also do it before you set any parameters in shared memory (in
case you're doing so) otherwise they'll be cleared before you run hashpipe.
Mark Ruzindana
On Thu, Dec 17, 2020 at 3:37 PM Mark Ruzindana wrote:
> Just another note which is a little simpler. I haven't thought ab
tance number*" command right before you run hashpipe.
What I said before was still relevant, but your particular issue might be
this simple.
Good luck again!
Mark Ruzindana
On Thu, Dec 17, 2020 at 11:31 AM Mark Ruzindana wrote:
> Hi Ross,
>
> I think I have a solution to your pro
ou can write your own, whichever works.
Hopefully this helps. If this isn't your problem, maybe provide a few more
details if you can, and maybe I can help.
Good luck!
Mark Ruzindana
On Wed, Dec 16, 2020 at 11:08 PM Ross Andrew Donnachie <
radonnac...@gmail.com> wrote:
> Good da
Also, I tried to condense/summarize the issue so if you would like
additional details, please feel free to ask and I'll provide them.
Thanks again,
Mark Ruzindana
On Tue, Dec 15, 2020 at 10:00 PM Mark Ruzindana wrote:
> Hi all,
>
> While running hashpipe with the intention of debugg
help.
Thanks,
Mark Ruzindana
On Thu, Dec 3, 2020 at 11:16 AM Mark Ruzindana wrote:
> Thanks for the suggestion David!
>
> I was starting hashpipe in the debugger. I'll use gdb and the core file,
> and let you know what I find. If I still can't figure out the problem, I
> will send y
some sort. If you can't figure
> out the problem from the core file, please create a "minimum working
> example" (well, in this case I guess a minimum non-working example),
> including a dummy packet generator script that creates suitable packets,
> and I'll see if I can recreate th
...'. And those numbers should
ideally be different for all of your threads. At least that's how I'm doing
things.
Hopefully that helps. If not, I might need a little more detail.
Mark Ruzindana
On Wed, Dec 2, 2020 at 8:06 PM Wael Farah wrote:
> Hi Folks,
>
> Hope everyone's doing we
ity since the code is quite dense, but I'm more than happy to share
more. I'm not entirely sure what I could share other than what I already
have to paint a better picture. Let me know what I could be missing if you
can.
Thanks again,
Mark Ruzindana
On Mon, Nov 30, 2020 at 4:54 PM John Ford wrote:
d and I got the same segmentation fault. So I
still think there's something about the implementation of the
release_frame() function that I'm not doing or it's not releasing the
frame. I'm not sure.
I appreciate any feedback. I'll respond ASAP if you have any questions.
Thanks,
Mark Ruzindana
On Fri, Oct
is called and I got the same segmentation fault. So I
still think there's something about the implementation of the
release_frame() function that I'm not doing or it's not releasing the
frame. I'm not sure.
I appreciate any feedback. I'll respond ASAP if you have any questions.
Thanks,
Mark Ruzindan
of 'X' you could use pkt_num+1 (i.e. a
> 1-based packet counter) so you'll know which bytes correspond to which
> packets. Using memset() would also eliminate reading from the packet
> socket blocks (another variable gone).
>
> Happy hunting,
> Dave
>
> On May 25, 2020,
elp.
Mark
On Mon, May 25, 2020 at 4:30 PM David MacMahon wrote:
> Hi, Mark,
>
> Sounds like progress!
>
> On May 25, 2020, at 13:56, Mark Ruzindana wrote:
>
> I have been able to capture data with the first round of frames of the
> circular buffer i.e. if I have 160 frames, I
the
release_frame function is freeing the memory entirely or there are some
priviledge issues that I'm unable to see.
Hopefully, my explanation makes sense. Let me know whether you need
additional information and I can definitely provide it. Thanks again for
the help.
Mark Ruzindana
On Fri, Apr 17
whether you need any more information or whether I'm not
stating anything clearly.
Thanks a lot for the help.
Mark Ruzindana
On Tue, Mar 31, 2020 at 5:08 PM Mark Ruzindana wrote:
> Thanks a lot for the quick responses John and David! I really appreciate
> it.
>
> I will definitely
y
> need data that is produced by a different core that's far away, NUMA-wise.
> And lock all the memory in core with mlockall() or one of his friends.
>
> Good luck with it!
>
> John
>
>
>
>
> On Tue, Mar 31, 2020 at 12:09 PM Mark Ruzindana
> wrote:
>
>> H
direction if you have
any insight?
If you need anymore details, please let me know. I didn't add as much as I
could because I wanted this to be a reasonably sized message.
Thanks,
Mark Ruzindana
--
You received this message because you are subscribed to the Google Groups
"c
16 matches
Mail list logo
