From: amirali.shambayati@gmail.com (Amirali Shambayati)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel list data structure
Date: Sun, 12 Jun 2011 20:12:33 +0430 [thread overview]
Message-ID: <BANLkTimUQEwyMg7JXjg+ohGM4-JT4KLNVw@mail.gmail.com> (raw)
In-Reply-To: <20110607015141.GA24249@internetdog.org>
Hello all,
I debugged my code (which I explained in previous mails), and I found out
this:
In the function which I add bundles to writeQueue and requests to bundle,
everything goes well and it seems that, this structure works well.
But! in another function(which its task is dispatching requests to lower
level), as I traverse in reqsQueue, in bundle, requests which have already
been added to list are not available!
Any idea?
Regards,
On Tue, Jun 7, 2011 at 6:21 AM, Ali Bahar <ali@internetdog.org> wrote:
> On Mon, Jun 06, 2011 at 10:43:20AM +0430, Amirali Shambayati wrote:
> > Ali thanks for your valuable comments. Would you suggest me an
> alternative
> > method to implement the structure I explained?
>
> I don't know, sufficiently, what you _intend_ to implement. As
> described originally,
>
> > > > "noop_data" has a reference to start point of bundles list, called
> > > > "writeQueue"
> > > > "bundle" has a reference to start point of requests list, called
> > > > "reqsQueue".
> > > > "bundle" knows its related list using "bundlesQueue".
> > > > "request" knows its related list using "queuelist". (request struct
> is
> > > > already implemented in kernel)
>
> your data structures are capable of fitting what you say; however,
> they may not match that which you have visualized in your mind. It'd
> take even more guess-work on my part to divine the latter.
>
> Let me go out on a limb here, and suggest the following.
>
> I don't think you have any kernel-specific issues. This is the sort of
> thing which is best handled by sitting down with someone, and
> articulating what you have in mind. The bugs (in your
> visualization-to-implementation) are then sure to come out.
>
>
> > Sharif University of Technology
>
> Judging by the word of mouth, and the grad students I've seen, Sharif
> should be full of exceptionally bright students. Grab the guy next to
> you, and talk it out.
>
> later,
> ali
>
--
Amirali Shambayati
Bachelor Student
Computer Engineering Department
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110612/5c84a79c/attachment-0001.html
next prev parent reply other threads:[~2011-06-12 15:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 13:39 kernel list data structure Amirali Shambayati
2011-06-06 1:47 ` Jonathan Neuschäfer
2011-06-06 2:19 ` Ali Bahar
2011-06-06 4:00 ` Ali Bahar
2011-06-06 1:59 ` Ali Bahar
2011-06-06 5:35 ` Ali Bahar
2011-06-06 6:13 ` Amirali Shambayati
[not found] ` <BANLkTin1yNceh7d6d8AdTqDCiSmFxp976A@mail.gmail.com>
2011-06-06 6:31 ` Amirali Shambayati
2011-06-06 8:16 ` Amirali Shambayati
2011-06-06 14:31 ` Jonathan Neuschäfer
2011-06-07 1:51 ` Ali Bahar
2011-06-12 15:42 ` Amirali Shambayati [this message]
2011-06-13 10:57 ` Amirali Shambayati
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTimUQEwyMg7JXjg+ohGM4-JT4KLNVw@mail.gmail.com \
--to=amirali.shambayati@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).