From: Gary Benson <gbenson@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [pushed] [PATCH v2] Associate target_ops with target_fileio file descriptors
Date: Wed, 25 Mar 2015 11:32:00 -0000 [thread overview]
Message-ID: <20150325113201.GA8977@blade.nx> (raw)
In-Reply-To: <551196FA.7020702@redhat.com>
Pedro Alves wrote:
> Because there's no point in starting the next lookup at the
> handle we just opened if we're reusing a slot, either. And
> then that allows getting rid of the VEC_address, by simply
> doing that increment at the end:
>
> /* Index into fileio_fhandles of the lowest handle that might be
> closed. This permits handle reuse without searching the whole list
> each time a new file is opened. */
> static int lowest_closed_fd = 0;
>
> static int
> acquire_fileio_fd (struct target_ops *t, int fd)
> {
> fileio_fh_t *fh, buf;
>
> gdb_assert (!is_closed_fileio_fh (fd));
>
> /* Search for closed handles to reuse. */
> for (;
> VEC_iterate (fileio_fh_t, fileio_fhandles,
> lowest_closed_fd, fh);
> lowest_closed_fd++)
> if (is_closed_fileio_fh (fh->fd))
> break;
>
> /* Push a new handle if no closed handles were found. */
> if (lowest_closed_fd == VEC_length (fileio_fh_t, fileio_fhandles))
> fh = VEC_safe_push (fileio_fh_t, fileio_fhandles, NULL);
>
> /* Fill in the handle. */
> fh->t = t;
> fh->fd = fd;
>
> /* Return its index, and start the next lookup at
> the next index. */
> return lowest_closed_fd++;
> }
That's nice, I pushed that one, thanks!
Gary
--
http://gbenson.net/
prev parent reply other threads:[~2015-03-25 11:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 13:21 [PATCH] Encapsulate " Gary Benson
2015-03-18 15:51 ` Pedro Alves
2015-03-18 18:45 ` Gary Benson
2015-03-20 16:06 ` [PATCH v2] Associate target_ops with " Gary Benson
2015-03-24 13:22 ` Pedro Alves
2015-03-24 16:17 ` Gary Benson
2015-03-24 16:36 ` Pedro Alves
2015-03-24 16:55 ` Pedro Alves
2015-03-25 11:32 ` Gary Benson [this message]
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=20150325113201.GA8977@blade.nx \
--to=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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